How to better support PIP requirements.txt

We recently pushed a new version of VersionEye online. The new version comes with an improved parser for requirements.txt files.

ImageThe new features include:

  • Comments in requirements.txt files can be handled.
  • Lines starting with http:// or https:// will be ignored.
  • Handling of entries without explicit version string.
  • pip.log file support.

Here is a simple example of an entry:


But other comparators work, too now. Like this one here:


Or in case you have only the package name, like this:


The new version can handle the pip.log file. Simply upload it or put in the URL and all the dependencies in the pip.log file will be shown.

Check it out and we’d love to hear your feedback.

Berlin: LinuxTag 2013

LinuxTag 2013, the biggest Linux and Open Source Conference in Europe, takes place from May 22 – 25, 2013 in Berlin. Join workshops & tech talks and don’t forget to check out the big exhibition hall, where you can meet some of the vendors. It’s a place where .com meets .org.

VersionEye’s founder and CEO, Robert Reiz, will be there for two more days on Friday and Saturday. You can find him at the Yunicon stand in the exhibition hall. Btw Yunicon is an awesome private cloud provider from Berlin and they have by far the coolest exhibition booth. Why? Because they have FREE drinks! Do we need to say more?  :-)


Robert is doing a daily tech talk about “Continuous Updating” with VersionEye at 3:30 pm. 


Join the talk if you’re curious to learn something about “Continuous Updating”, VersionEye, or even if you just want to grab a free drink. Robert will be more than happy to answer your questions.


Hope to see you around!

VersionEye’s new Dependency Badges

We are happy to announce that VersionEye now provides new dependency badges for Java, Ruby, PHP and Node.JS. They are available on every package page and look like this:


With the help of the badges you can see immediately if the dependencies of a software library are up-to-date, out-of-date or unknown. Click on the badges and a pop-up window will appear with code snippets for mostly used markup languages. To add the badges to your GitHub or other HTML pages, simply copy and paste.

Good news: The badges are also available for your public VersionEye projects.


You know a project is up-to-date when all of a project’s dependencies are up-to-date.

Can’t wait to see these badges on GitHub!  :-)

VersionEye refactored the usage of GitHub API scopes

Did you know that VersionEye provides login with your GitHub account? Initially we implemented the GitHub login with the “repo” scope. This implies that VersionEye obtains access privileges (reading and writing) to ALL your repositories, even your private ones. You may ask yourself, why does VersionEye need access privileges to my private repositories? The answer is simple: VersionEye doesn’t need writing authorization. We will never touch your source code. Promise! Unfortunately GitHub API currently doesn’t provide a “read-only” scope. But we were talking to the GitHub guys at the GitMerge Conference in Berlin and they told us that more scopes for the GitHub API are in progress.

You may be also interested to know, why VersionEye even needs read access to your private repositories? Well, there is no way around it, if you want us to monitor your private repositories.

Many people complained about this scope. So, we did some refactoring, since VersionEye likes to help. If you’ve ever tried to login via GitHub, you know that VersionEye only asks for read access to your public repositories.

ImageGood to know: VersionEye will only convey your public repositories, when you create a new project.

ImageBut you’ll be able to grand VersionEye access to your private repositories retrospectively, if you want us to monitor those. Just click the link “Grand access to private repositories” on the GitHub tab and you’re going to see this:

ImageAnd keep in mind, VersionEye will never change your repositories! All we do is reading and monitoring your private repositories.

Click on the “Connect” link in the preference window, to see your connections to other social networks. Here you can also see the GitHub API scope that we have set for your account.

ImageUse the “disconnect” link anytime and your GitHub token in the VersionEye database will be deleted.

Improving the Dependency Wheel at GitMerge Hackathon

Improving the Dependency Wheel at the GitMerge Hackathon

Last week VersionEye’s founder Robert Reiz attended at GitMerge Conference in Berlin, sponsored by GitHub and Google. Saturday was hackathon day and Robert found somebody who wanted to contribute to the dependency wheel project. Many thanks to Coding46 for his contributions!

The dependency wheel project is a JavaScript Library which enables you to draw a circle of dots and connect the dots according to his dependencies …

Read more

VersionEye: We’ll keep you up to date!