Package maintenance · the most-downloaded packages
What share of the most-downloaded packages have had no release in over two years?
19% of the most-downloaded packages (95% CI 16.43–21.86%), measured across 800 packages on 2026-11-15.
A minority · a fraction of the global rate of 39% · little changed since 8 November
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
- long-tail (packages)96.43%
- packages with a native build step96.11%
- npm (packages)57.39%
- all packages39.15%
- top100m+ (packages)20.89%
- top10m+ (packages)8.26%
- pypi (packages)8%