KPI’s for software libraries

Have you seen VersionEye’s new detail view for our software libraries? We just launched it this week.

Image

Enjoy the new, clearer view and check out important KPIs for software developers on the right side. For example, you can see how many days/weeks/months/years ago the selected version of the library was released. Let’s say the current version was released 1 year ago, so it’s very likely that the project is no longer maintained and you shouldn’t use software libraries that are not maintained anymore.

We also have a KPI that shows the average release time. In general, if the average release time is less than 1 month and the current version was released less than 1 month ago, you can assume that the project is still active. You are able to report bugs, change requests and the core committers will reply and help you.

Another KPI for a high quality software library is the number of references. If there are 10K other artefacts referencing a software library it is very likely that the project is great.

We would love to hear your feedback on that. So let us know what you think.

2 thoughts on “KPI’s for software libraries

  1. I’m new to the site and I really like what I’ve seen so far. Great job!

    One thing though, I was sad to learn that the number of references to the library can’t be enumerated. It would be insanely great to see a list of those projects that depend on the current library. Are there future plans for this feature? It would be killer!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s