What should you do when opensource package is not maintained anymore

Imagine you are using some npm or pip package and you feel it is outdated or it just says somewhere "is not maintained anymore". What should you do first - find out whether there is someone else who already started maintaining,let me show you how to do it πŸ˜‰

How to understand the package is not maintained anymore

First, find the page of interested package on source code hosting website.

I will consider [email protected] package for npm, I know that I am using exectly this package by package.json or package-lock.json file.

To find the opensource hosting page, first we should find package name on https://npmjs.com with exact name.

NOTE: Name is very important when you try find a package sources page☝. Please carefully follow the sequence otherwise you can mix up a packages and all your effort will be lost. This happens very often

Now look at Repository or Homepage:


Here we see so "dead" package:

First solution to try when "repo is not maintained anymore"

Click on forks number:


And find out the most popular fork. To understand popularity faster we might assume that more popular fork will have more forks. So we should just find longest fork chain:


So we've found https://github.com/vusion/webfonts-generator by vusion which also re-published it to a new npm package:

npm install --save-dev vusion-webfonts-generator

Here how it works. In worst case you can fork a project and start maintaining it or just use by yourself for your fixes✌

#npm #pip #opensource
menu 18
Bruce Hardy profile picture
Oct 25, 2020
by Bruce Hardy

Best related

Other by Bruce Hardy