Software projects have a lot of open source dependencies nowadays and we as developers are in need of more tools to help us keep on top of all of those dependencies.

As a developer, you need ways of finding out if any libraries used are incorrectly licensed, marked as deprecated or unmaintained by their authors, or have potential security vulnerabilities.

It can be time consuming to manually review all of those dependencies so often developers don’t bother, which over time can lead to some serious technical and potentially legal debt in their code bases.

When the time comes to do due diligence or compliance checks you might find out that you’re heavily dependent on a library with a conflicting or missing license which could mean having to rework the code that depends on it.

Dependency CI integrates directly into your GitHub workflow just like a traditional CI system, running a set of configurable tests on any dependencies it detects in the code base. It checks for unlicensed, deprecated or unmaintained libraries that your code depends upon.

This works great with GitHub pull requests allowing you to find any potentially bad dependencies being added.

Dependency CI shows up right in the GitHub interface as you review pull requests, ensuring any issues are highlighted before you merge and ship the code to production.

It’s built on top of Libraries.io, which gives it access to metadata on over 1.5 million open source libraries. Libraries.io is updated over 200 times per day with the latest updates from every package manager which means it always has the latest information.

Dependency CI currently supports dependency checks from 21 popular package managers including NPM, Rubygems, Maven, CocoaPods, Packagist, Bower and NuGet.

Sign up today and get a better picture of your dependencies