Package maintenance · npm (packages)

What share of packages on npm have had no release in over two years?

57.39%

57.39% of packages on npm (95% CI 53.65–61.05%), measured across 683 packages on 2026-11-15.

About half · well above the global rate of 39% · down 1.0 points since 8 November

active (<1y): 35.72%stale (1–2y): 6.88%abandoned (2y+): 57.39%
active (<1y) · 35.72%stale (1–2y) · 6.88%abandoned (2y+) · 57.39%
Trend

Measured every Sunday since 2026-08-01 — 19 observations to date. Last measured 2026-11-15.

How this is measured

Bulk registry metadata; last release date. active < 365 days, stale < 730, abandoned ≥ 730.

Built entirely from public bulk feeds — no target is contacted. Aggregate-only. 95% Wilson confidence intervals. Population: the most-downloaded packages per ecosystem plus a native-build stratum, from public registry metadata. Snapshot: packages-top400.

Licensed CC BY 4.0 — reuse with attribution to Quiet Failures. Download: JSON · CSV.

Why it matters

A widely-depended-on package with no release in two years is installed everywhere and maintained by nobody — no security fixes are coming, and the dependency graph gives no warning. Being unmaintained is invisible at install time.

Limits of this measurement

A mature, complete library can be legitimately quiet; release cadence is a proxy for maintenance, not proof of abandonment.

The same check, other segments

Share or cite this figure

Reuse is free under CC BY 4.0 — attribution to Quiet Failures is all we ask.

Post on X

Embed this stat

Free to reuse under CC BY 4.0 — the card links back and updates as the data does.

<iframe src="https://quietfailures.com/embed/pkg-maintenance/ecosystem-npm" width="380" height="210" style="border:0;max-width:100%" loading="lazy" title="What share of packages on npm have had no release in over two years?"></iframe>