Package maintenance · top100m+ (packages)
What share of packages in top100m+ have had no release in over two years?
21.46% of packages in top100m+ (95% CI 18.63–24.59%), measured across 727 packages on 2026-08-09.
Measured every Sunday since 2026-08-01 — 5 observations to date. Last measured 2026-08-09.
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.