Project Collaborators

VersionEye can watch your projects on GitHub, Bitbucket or Stash and notify you about out-dated dependencies. Most time you don’t work alone on a project. Most time you have other team members who work with you on a project.

With the collaboration feature you can add collaborators to your project at VersionEye and they will receive the notification emails as well, just like you do. Just navigate to your project and click the “Collaborators” tab. Here you can start typing the name or username of the user you would like to add.

Screen Shot 2014-11-27 at 11.16.15
VersionEye will show you some suggestions. By clicking on “Add collaborator” the selected user is added immediately as a collaborator to your project and he/she will receive email notifications to the project. The collaborators receive the email notifications to their primary email address in the same period as the you, the project owner, do.

If you would like to add somebody who is not a user at VersionEye yet, you can simply type in an email address and VersionEye will send out an invitation email immediately.

Under the menu “Shared with me”. You can see all the projects you are added as a collaborator. If you don’t like to be a collaborator in a project, simply hit the “remove” button to leave the project and you will not receive anymore notification emails to that project.

Screen Shot 2014-11-27 at 11.23.03

In VersionEye Enterprise there is no “remove” button. That’s a feature 😉 If you don’t want to receive the emails you have to talk to the project owner that he removes you from the list.

Let me know how this feature works for you.

New Project Notification Emails

Up to now VersionEye sent out one notification email for each of your projects. That was not the best solution, specially for power users with 100+ projects because they got A LOT of emails. The new version only sends out 1 single email with a summary.

Assume you have 100 projects in VersionEye. 50 of them are monitored daily, and the other 50 are monitored weekly. In that case you receive now every day just 1 single email with a summary about your daily monitored projects. That looks similar like this one here.

Screen Shot 2014-11-25 at 18.03.19
The Dependencies column shows how many dependencies in the project are out-dated and how many are unknown. The Licenses column shows how many dependencies violet the license whitelist and for how many dependencies VersionEye doesn’t know the license.

By clicking on the project name you come to the project detail page on VersionEye, where you can see all dependencies of the project with more details.

Now you get less emails and a better oveview.

New Project Overview

Up to now the project overview at VersionEye was a bit cluttered, it was hard to see which project has the most out-dated dependencies. The new project overview delivers a much more clear design in a table layout.


The table is sorted by out-dated dependencies. The project with the highest number of out-dated dependencies is always on the top. Now you can see immediately which project needs most of your love 🙂

Let me know how you like and what do you think about this new view.

How we improved our search results

As developers we try to not write all code by ourselves but to rather reuse existing code in the form of libraries (or “libs” for short). A key activity for code reuse is to search and find libraries that do what you need. That’s why searching through more than 200,000 libraries is one of the key features of VersionEye.

As you might have noticed, we already improved the search results on VersionEye dramatically. Currently, we are tracking almost 300K open source libraries. Many of them have similar or even the same names. Let’s assume you do a search for “hibernate”. There are more than 400 open source packages which include the string “hibernate” in their name. But which one is the one you are looking for?

Up to now, we only ranked search results by the best match for “name”. But this was often disappointing, as the results weren’t ranked the way you would think they should be ordered.

That’s why we came up with two important changes for the search. We included the number of followers and the number of references into the search algorithm. Now, when you search for “hibernate” you will see this:

Screen Shot 2013-11-16 at 18.26.45

As you can see there is a perfect match ranked 3rd place, a package with the name “hibernate”. The package with the name “hibernate-core” is now ranked 1st. It ranks higher because it has more followers and more references from other packages. That’s why we assume it is more important than the perfect match. And indeed this is the package you are looking for most of the time you search for “hibernate”, right?

Now, these are the search results for “spring”

Screen Shot 2013-11-16 at 18.46.20

All the spring submodules come first, because they have a high number of followers and references. The perfect name match only ranks on place 12.

Those two small changes to the search algorithm have improved the search already dramatically. And the good thing is, you can influence the search results by your own. Every time you follow or unfollow a package on VersionEye you influence the search results.

If you have a question or an idea about any other factor that could improve the search ranking, please let us know in the comments.

VersionEye has moved to Potsdam

We did it again 🙂 This time we have moved from Berlin to Potsdam. Potsdam is pretty close to Berlin and with the train less than 1 hour away from our old office. We were lucky enough to get free office space from our investors Hasso Plattner Ventures. They had a spare yoga room and it seems like HPV is just not that into yoga 😉 So, we are using the room as our office now.

Here it is:



What do you think? It’s kind of cool to have our own office now. Although, it was inspiring to work in a coworking space, it is also very nice to close the door anytime we want and focus on our own work. There are no distractions anymore. Plus, we are very close to our investors, the Hasso Plattner Institut and the University of Potsdam. We also have a big lake, surrounded by a forest here. Quite idyllic.

Well, we can say that we like our new office very much and we are truly grateful to our investors that they let us stay in such an amazing office for free.

New email notifications

On VersionEye you can follow a software library and as soon the next version comes out you will receive an email notification. We don’t spam you. We send you 1 email per day with all the notifications to the software libraries you follow directly.

Now we changed the format a little bit. In the new email format we not only show you the new version, but also in which of your projects the software libraries is used. Here is an example how the new email looks like.

Screen Shot 2013-11-05 at 19.35.48

Of course this only works if VersionEye is monitoring some of your GitHub repositories.

Let us know how you like this new feature.


Today we want to present lat/lon. They are using our Maven Plugin to manage their Java dependencies.

Screen Shot 2013-11-05 at 13.31.14

lat/lon is a Germany-based consulting and software engineering company focused on Spatial Data Infrastructure (SDI), geospatial IT standards and Open Source software. lat/lon is a Principal Member of the Open Geospatial Consortium and the main developer of the degree project ( ), the most substantial implementation of OGC and ISO standards in the field of Open Source software. It builds the foundation for numerous productive components of spatial data infrastructures – in Germany, Europe and all over the world.

New Endpoints on our API

We just recently added new Endpoints to our API for a better GitHub Interaction. Here is a screen shot of the new Endpoints.

Screen Shot 2013-11-05 at 11.35.43

You can check them out here:

This new Endpoints are used by our ruby command line tool to add GitHub repositories to VersionEye. The command line tool is completely open source and on GitHub. It’s still early alpha and we are seeking for feedback. Your feedback and pull requests are very welcome 😉

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!