Greenkeeper has said goodbye 👋 on June 3rd, 2020! Read more below…


Automated dependency management

Greenkeeper has said goodbye 👋 !

We’re passing the torch on to Snyk, and we’d like you to join in 💖

An Important Message from the Makers of Greenkeeper

We’ll stop Greenkeeper’s operation as an independent service on June 3rd, 2020. For your dependency update needs, we have a brilliant alternative for you: Snyk. The team behind Greenkeeper have spent the past months working with them on next-generation dependency updates as a part of their open-source security product. We invite all of our users to migrate over: Snyk not only has a generous free plan for Open Source repos and small organisations, but also offers dev-friendly security features that Greenkeeper didn’t have. They’re good people, and your repos will be in competent and caring hands.

What happens to my Greenkeeper account?

Before we explain all the how, why and what next: you can easily migrate your Greenkeeper account over to Snyk, from today until the 3rd of June 2020, when Greenkeeper will shut down. Moving to Snyk is opt-in: no-one will be migrated against their will. We’ll answer all your questions concerning your data, feature parity, existing billing periods, plan and pricing differences etc. further below.

All of us have had services we use and love go away at some point, and we’re well aware of the disruption this can cause. We know we won’t be able to make everyone happy, but we’ve worked hard on the migration, and we’re doing our best to make the process as open, transparent, painless and simple as possible 🌅

So what happened and how did we get here?

When we started out in 2015, Greenkeeper was one of the first dependency update services. In the following years, several competitors appeared, and last year, dependency updates finally arrived in the mainstream: on platform level, and as part of larger services. We realised that we also needed a larger partner to keep up with this development.

Since it isn’t feasible to just take Greenkeeper and plug it into Snyk, we’ve teamed up with them to build a new generation of dependency update service that is an integral, seamless part of Snyk. This also means that we’ll be focusing on this in the future, building the dependency update service we’ve always wanted to, and saying goodbye to Greenkeeper as you know it.

Who are Snyk?

Snyk helps over 400,000 developers worldwide find and fix vulnerabilities and license issues in their open source dependencies and containers. They truly care about automation, the developer workflow, and doing genuine good in the Open Source community while making it safer and more secure. We honestly couldn’t be more happy about this partnership: not only do we agree on how dependency updates should work, our two companies are also well aligned in terms of values 🤝

What’s the roadmap now?

Why Snyk and Greenkeeper?

How do Greenkeeper and Snyk compare in terms of functionality?

How do I migrate to Snyk?

What happens if I don’t migrate to Snyk?

That’s all.

We’d like to thank all past and present customers and Open Source users for their trust in pioneering automated dependency updating, and one of the first automated development tools overall. We have changed the industry in a big way and we couldn’t be more happy to make our impact permanent by joining forces with Snyk.

From all of us here at Greenkeeper, farewell! 🤖🌴💚