How to Tell If an npm Package Is Abandoned

Check the deprecated flag first, then the last release, the repo, and who still holds publish rights.

To tell whether an npm package is abandoned, check four things in this order: whether the author marked it deprecated (npm view <pkg> deprecated), when it last published a version (npm view <pkg> time.modified), whether its source repository is archived, and whether the accounts that can still publish it have been active recently. A package can be finished rather than abandoned, so the last two matter more than the date alone.

1. The deprecated flag

Authors can mark a package or version deprecated (npm docs). npm prints the message on install, but it scrolls past in CI logs. Ask for it directly:

npm view left-pad deprecated
# use String.prototype.padStart()

If this prints anything, the author has told you to leave. That is the clearest signal there is.

2. Last publish date

npm view left-pad time.modified

No release in a year is a prompt to look closer, not a verdict. Small, finished utilities often go years without needing a change.

3. Is the repository archived?

Follow npm view <pkg> repository.url. An archived GitHub repo is read-only: nobody is going to merge a fix. OpenSSF Scorecard’s Maintained check gives an archived project its lowest score and the highest score to one with at least one commit a week over the previous 90 days. deps.dev shows Scorecard results per package.

4. Who can still publish it

This is the check most people skip, and the one attackers care about. An abandoned package whose old maintainers still hold publish rights is a target: one phished or reused password and a new version goes out to everyone. npm view <pkg> maintainers lists the accounts; it does not tell you when they last did anything.

Commit, our CLI, does that part. It reports publisher count, weekly downloads, age and provenance, and warns about publishers who still have access but have gone quiet:

npx proof-of-commitment <package> [<package> ...]
npx proof-of-commitment --file package-lock.json

On left-pad today it warned “no release in 12+ months” and listed two publishers with current access who had been inactive for years.

Where Commit falls short here

In the same run Commit did not show left-pad’s deprecation message. Check 1 above caught it; Commit did not. So run npm view <pkg> deprecated yourself, or use a tool that surfaces it: Socket lists Deprecated and Unmaintained among its maintenance alerts.

Commit is our tool, so weigh what this page says about it accordingly. The commands and behaviour here were run on November 4, 2026; registry data changes, so re-run them rather than trusting a number on this page.