VersionEye Dependency Badges

VersionEye now has dependency badges for Java, PHP, Ruby and Node.JS.  You can find them on every package page.  They look like this:

dep_out-of-date dep_unknown version_up-to-date

When you click on one of these badges, a pop-up will appear with some sample code showing you how to integrate the badge into your page.  These are some examples for the most commonly used meta languages such Markdown, Textile, RDoc and HTML.

Screen Shot 2013-04-24 at 5.27.56 PM

We have badges for every Java, PHP, Ruby and Node.JS open-source library you can find using the public search on VersionEye.  In addition, we offer these badge for your private projects at VersionEye.  And as soon as you turn your VersionEye project public, you can embed the badge into other pages as well.

Screen Shot 2013-04-25 at 3.31.20 PM

We consider a project to be stable if all of its dependencies are using the latest stable version.

We are looking forward to seeing these badges on many GitHub pages 🙂
We keep you informed

Table View for Dependencies

We just pushed a new version online. The Dependencies are now displayed in a table view. This is how it looks for Hibernate-Core.

Screen Shot 2013-04-15 at 6.30.04 PM

You can see immediately which dependencies are outdated.

We did the same for private projects. Here is an example how it looks now.

Screen Shot 2013-04-15 at 6.29.03 PM

This view is more compressed and you can see more details without scrolling.

VersionEye: We’ll keep you up to date!

Merchants – what is your ecommerce strategy?


All Merchants;

By now, you should realize the value that ecommerce brings to any business…
– what is your ecommerce plan? do you have one?

Good article: eCommerce strategy ideas…

” Make it a great shopping experience, everytime… ”

eCommerce / Mobile payments specialist / for your Free demos

View original post

Minimum Stability

The PHP package manager Composer has a very cool feature called minimum stability. It defines the minimum stability of wildcard versions.

Let’s say you define the following in your composer.json file:

“symfony/finder” : “2.2.*”

By default, the minimum stability is “stable”. That means the package manager will look for the newest version in the “2.2.” branch which is stable. If you are looking for the newest dev version you can redefine the minimum stability for this package to:

“symfony/finder” : “2.2.*@dev”

In that case you would get the newest development and unstable version of the “2.2.” branch. Possible stability tags are “@dev”, “@RC”, “@stable”, “@beta” and “@alpha”.



now understands the minimum stability tags Composer uses and can handle them. But it is an early implementation. Your feedback is highly welcome!

Updating an existing VersionEye project using API

The VersionEye API enables you to create a project using the API. All you need to do is use POST to send your project file to the “/v1/projects.json” endpoint. VersionEye then creates a new project for it and returns a JSON with the used libraries and any outdated information.

There is already an add-on for the Symfony Developer Toolbar:


And one for the Zend Dev. toolbar:

These modules send your composer.json file to the VersionEye server.  Unfortunately, the first version created a new project at VersionEye each time there was a post. This is not the desired behavior. We added a new endpoint to the API which enables API developers to update existing projects.

The process now looks like this. First, you upload the composer.json file via POST to this resource: “/v1/projects.json“. In the response, VersionEye returns a “project_key” for the project. Next, you send the composer.json file via POST to this new resource: “/v1/projects/{project_key}.json“.

Screen Shot 2013-03-25 at 10.05.20 AM

The new endpoint, “/v1/projects/{project_key}.json”, does not create a new project. It only updates an existing project. Please use it in the future to update an existing project.

Subscribe to Your Software Libraries via RSS

We finished the RSS feature for VersionEye. You can now subscribe to your libraries via RSS. On your profile page, there will now be an RSS icon next to your favorite packages.


Simply click on the icon and you will always receive the latest version notifications via your favorite RSS reader. I use RSS Toaster.


And the cool thing is that you are now also able to get the notifications on your smart phone.


Or on your favorite tablet.


Please let us know if you have questions.

How to get a list of all Licenses of your Software Project

The new VersionEye API enables you to fetch a list of all licenses of your software project.  VersionEye now supports 7 different package managers. In my example, I use a Ruby Gemfile to show how easy it is to get the license list.

First of all, you need to sign up at VersionEye to get your API_KEY.  The key is free and the whole process takes less than 30 seconds.  As soon as you have your API_KEY, you can take full advantage of the VersionEye API.

The “/api/v1/projects.json” resource supports file uploads via the API.

Screen Shot 2013-02-16 at 3.39.11 PM

Send your Gemfile via POST to this resource and you will receive a JSON object with all the dependencies in the file.

Screen Shot 2013-02-16 at 3.39.35 PM

The JSON response contains a “project_key”.  This project key is unique for each user.  You can use it to fetch all licenses of the project.  All you need to do is send a GET request to “/api/v1/projects/PROJECT_KEY/licenses.json?api_key=API_KEY” and you will receive the license list as JSON.

Screen Shot 2013-02-16 at 3.40.14 PM

That’s it.  You only need two requests to get the license list.

Please let me know what you think of this feature.

Getting a Project License List in less than 1 minute

In a regular project you normally use a handful of software libraries and every library in your
project can use a different license. Getting a list of all the licenses used in your project can be
difficult. One option is to manually double-check the license for every single library in your
project. But that is time intensive and a pain in the ass!

VersionEye offers you a quick solution for that problem. You can get the license list in less
than 1 minute. After logging in, you are in “My Projects”. Now click on the link “Add New
Project” in the left navigation bar to create a new project.

Screen Shot 2013-02-04 at 5.40.07 PM

Upload a project file. This might be a pom.xml, Gemfile, composer.json, package.json,
dependency.gradle or another supported file with your dependencies. As soon as the upload
is completed, you will see a tab with all the dependencies.

Screen Shot 2013-02-04 at 5.40.53 PM

Now all you have to do is to click on the “License” tab to see all licenses in this project. And
here they are.

Screen Shot 2013-02-04 at 5.41.17 PM

In the example above, most libraries use the MIT license. Some of them are licensed under
“Ruby” and for one library, VersionEye has not been able to detect a license.

At present, we are extracting the license information directly from their repository managers
(Maven, RubyGems, Packagist and so on). But at the same time, we are working on crawlers
crawling license infos from SMCs such as GitHub and co.

It’s that simple. Let me know if you have questions regarding this process.

VersionEye: We’ll keep you up to date!

Language Statistics : Java and Ruby are leading

VersionEye tracks open source software libraries.  We are not interested in source code but in releases that are already finished.  Or in other words: In artifects that are „completed“ and which you can use in your projects.  The graph below shows the number of projects tracked per language.

Screen Shot 2013-01-29 at 7.05.14 PM

These figures are compiled from more than 50 different repository servers in the Internet, including repository servers such as,, and more than 40 Maven repository servers.  SCM tools such as GitHub or BitBucket have not been taken into consideration.

The graph only shows software library projects.  It does not include desktop tools written in Java and hosted on SourceForge.

In the next graph, you can see the growth of the repositories over time.

Screen Shot 2013-01-29 at 7.05.35 PM

VersionEye only started crawling repositories in April.  That is why we cannot go back any further in time.  However, the last months are already enough to show the speed in which the repositories grow.  If RubyGems keeps on growing in that pace, it will soon be no. 1.

On VersionEye‘s website, you will always find the latest graphs (updated on a daily basis):

We keep you informed.