What's the bus factor situation in JavaScript?

The 2025 ICSE paper 'Understanding the Response to Open-Source Abandonment' found that 15% of widely-used npm packages become abandoned within a six-year observation window. The Tidelift 2024 survey found that 60% of maintainers (across all languages) have quit or considered quitting, with JavaScript and TypeScript slightly above the average. Bus factor 1 is the default for solo JS projects. A solo JS project with no release in 12 months and unanswered issues is the typical adoption candidate.

What if the JS maintainer is on vacation and just hasn't released?

Don't assume abandonment from a single quiet month. Send a polite issue, wait 30 days, then escalate. JavaScript's release culture is 'ship often,' so 3+ months of no release on a library that used to release monthly is a real signal. If 6-12 months of silence + unanswered issues + bus factor 1, it's a candidate for adoption. Otherwise, wait — the maintainer may come back.

By language · JavaScript

Abandoned JavaScript projects looking for a new maintainer

Q: How do I find abandoned JavaScript projects?

Three places: (1) the BreakPoint feed filtered to JavaScript; (2) GitHub topic search for adopt-me filtered to language:javascript; (3) npm CLI: `npm view time` to see the last release, and `npm view deprecated` to see if the maintainer has formally deprecated it. Snyk Advisor (snyk.io/advisor) scores every npm package on maintenance, security, and popularity — a quick triage tool.

Q: How do I deprecate an npm package I'm stepping away from?

Use `npm deprecate "This package is no longer maintained. Use instead."`. The message shows up on every npm install of the package. Also set the `deprecated` field in package.json. The deprecation does NOT delete the package — it just warns. Don't delete the package. If you want to fully archive, use `npm deprecate` plus a clear 'this project is no longer maintained' README banner.

A 2026 field guide to finding, evaluating, and adopting an abandoned npm package. Covers the npm deprecate workflow, the GitHub adopt-me topic, and how to read the maintenance signals in your package.json.

Published July 13, 2026 · ~3 min read

The short version

Use npm deprecate <package> "message" when stepping back — it surfaces a warning on every install.
The canonical signal vocabulary is the GitHub adopt-me topic + the looking-for-maintainer shield + a pinned issue.
15% of widely-used npm packages become abandoned within 6 years (2025 ICSE study). Bus factor 1 is the default for solo JS projects.
For evaluation, check Snyk Advisor + npm view <package> time + GitHub git shortlog.

How to find abandoned JavaScript projects

The fastest way is the BreakPoint feed filtered to JavaScript. Three other signals to layer on top:

GitHub topic search: https://github.com/topics/adopt-me?l=javascript — direct, real-time.
npm CLI: npm view <package> time shows the last release date. npm view <package> deprecated shows the deprecation message. npm view <package> maintainers shows the bus factor.
Snyk Advisor: scores every npm package on maintenance, security, and popularity. A "low maintenance" score is a real adoption-candidate signal.

The npm deprecate workflow

If you're stepping back from a JavaScript project, the npm-native way to signal it is npm deprecate <package> "<message>". The message shows up on every npm install of the package, which is the right place to surface it. A good message includes (1) when the deprecation started, (2) what to use instead, (3) a link to a migration guide. Also set the deprecated field in package.json. The deprecation does NOT delete the package — it just warns. The package continues to install and work for everyone who depends on it, with the warning visible to anyone adding it to a new project.

If you want to fully archive the project (the equivalent of a GitHub archive), use npm deprecate plus a clear "this project is no longer maintained" banner in the README. Don't npm unpublish unless the package is less than 72 hours old — npm blocks unpublishing of older packages to protect dependents.

If you maintain: how to signal "looking for a maintainer"

See the maintainer handoff guide for the full 5-step playbook. The JavaScript-specific bits: add the adopt-me GitHub topic, add the shields.io looking-for-maintainer badge to the README, pin a "Seeking new maintainer" issue, run npm deprecate for users who depend on you, and drop the project on BreakPoint. JavaScript's release culture means a 3-month silence is already a real signal — don't wait until the issues queue is unmanageable before you start the handoff.

Frequently asked questions

How do I find abandoned JavaScript projects?

Three places: the BreakPoint feed filtered to JavaScript, the GitHub adopt-me topic, and Snyk Advisor.

How do I deprecate an npm package?

npm deprecate <package> "<message>" — the message shows up on every install. Also set the deprecated field in package.json.

What's the bus factor in JavaScript?

Bus factor 1 is the default for solo JS projects. 15% of widely-used npm packages become abandoned within 6 years (2025 ICSE study).

How to find abandoned JavaScript projects

The npm deprecate workflow

If you maintain: how to signal "looking for a maintainer"

Frequently asked questions

Related reading