Health-index distribution
Latest health index of every inspected repository, in five-point intervals over the 1–100 scale.
median 67
Critical · 617At Risk · 1704Weak · 2203Moderate · 4576Good · 453645431612
Record in aggregate · metrics 2.10.0
The state of npm.
Aggregate statistics across every inspected repository publishing to npm — how health distributes, where the download volume sits, and which practices are common or rare, measured against the whole record.
Inspected repositories
19,791 of 19,792 indexed
Repositories with a published inspection report — the basis of every figure on this page. Indexed repositories without a first report are excluded.
Monthly downloads under inspection
476B registry-reported
Combined monthly package downloads across the inspected repositories, as reported by package registries. Registries that publish no monthly figure contribute nothing rather than zero.
Median health index
67 Good
The midpoint health index across the scope, computed under metrics 2.10.0.
Good or better
54% index 65 and above
Share of inspected repositories whose latest health index reaches the Good band (65) or higher.
Where the download volume sits
Combined monthly downloads by band, against repository counts.
58% of the monthly download volume under inspection flows through repositories below the good band — and the top 1% most-downloaded repositories carry 42% of the entire volume.
Repositories
23%23%23%
Download volume
19%19%17%
| Band | Repositories | Downloads / mo | Volume share |
|---|---|---|---|
| Exceptional | 1,612 | 58.1B | 12% |
| Excellent | 4,543 | 70.9B | 15% |
| Good | 4,536 | 69.9B | 15% |
| Moderate | 4,576 | 92.3B | 19% |
| Weak | 2,203 | 92.4B | 19% |
| At Risk | 1,704 | 82.2B | 17% |
| Critical | 617 | 10.7B | 2.2% |
Score shapes
The distribution behind each category median, in ten-point bins — where the record clusters, and where a category separates repositories or saturates.
Vitality76
1100
Community & Adoption50
1100
Sustainability & Governance60
1100
Engineering Quality70
1100
Security51
1100
AI Readiness61
1100
Category profile
Median category score across the scope. Ticks mark the whole-record median. Categories are documented in the methodology wiki.
The state of practice
Share of inspected repositories where the practice is publicly evident. Reports that predate a signal are excluded from its basis, never counted as missing.
Engineering & community practice
Agent-era signals
Signals read by the unweighted AI Readiness category.
Does popularity mean health?
Median health index (dot) and the middle half of repositories (band) per popularity bracket, on the shared 1–100 scale.
By GitHub stars
By monthly downloads
Security under the microscope
Average OpenSSF Scorecard result per check across the scope, weakest first, on Scorecard's 0–10 scale. Check results are mostly all-or-nothing, so the average tracks how much of the record passes. Checks Scorecard reports inconclusive are excluded from scoring, never counted as zero; each row's tooltip carries its basis.
Red flags
Findings that adjust a rating downward rather than scoring into it. Each is reported as a count, as a share of the whole record, and as a rate among the repositories where it could be determined at all.
A red flag needs its own evidence, so its basis is smaller than the record. Growth authenticity is assessed only where day-by-day history was collected; dependency findings only where a dependency graph resolved. Repositories the evidence cannot answer for are left out of the basis rather than counted as passing.
The pulse
How recently each inspected repository last saw a push, at inspection time.
Half of the inspected repositories saw a push within 4 days of inspection.
Push recency
79%
| Last push | Repositories | Share |
|---|---|---|
| Pushed within 30 days | 15,643 | 79% |
| 31 – 90 days | 1,836 | 9.3% |
| 91 – 365 days | 928 | 4.7% |
| Over a year | 1,384 | 7.0% |
Stewardship & resilience
Who stands behind the inspected repositories, and how many people the code depends on. Both are read by the governance category.
12,147Organization-stewarded median 75
7,644Personal accounts median 59
Maintainer bus factor
76% of inspected repositories depend on a single maintainer for the majority of their commits — including 1,986 with over a million monthly downloads.
The dependency iceberg
Declared direct dependencies against the full resolved graph (direct plus transitive), across the 14,045 reports with a collected dependency graph.
The median repository declares 6 direct dependencies — and resolves to 504 packages in total.
Resolved packages per repository
License landscape
The most common detected licenses across the scope (SPDX identifiers).
Most relied upon
The most-downloaded repositories under inspection publishing to npm — the records the figures above weigh heaviest. The rest is covered by the full catalogue · tag index.
npm
typescript-eslint/typescript-eslint
:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript
MITAug 27, 2026 · metrics 2.10.0
npm
npm/node-semver
The semver parser for node (the one npm uses)
ISCAug 29, 2026 · metrics 2.10.0
npm
jridgewell/sourcemaps
Monorepo for various sourcemap libraries
No licenseAug 29, 2026 · metrics 2.10.0
npm
babel/babel
🐠 Babel is a compiler for writing next generation JavaScript.
MITAug 27, 2026 · metrics 2.10.0
npm
eslint/js
Monorepo for the JS language tools.
BSD-2-ClauseAug 29, 2026 · metrics 2.10.0
npm
isaacs/minimatch
a glob matcher in javascript
BlueOak-1.0.0Aug 29, 2026 · metrics 2.10.0
Reading these figures
- Every figure is computed from the latest published inspection of each repository, under the versioned methodology (currently metrics 2.10.0). See the methodology · band scale.
- Statistics describe the inspected record — software admitted for inspection, not a random sample of all open source. Admission follows the public-interest criteria.
- Download figures come from package registries; registries that publish no monthly number (Maven Central, Go, NuGet, RubyGems) contribute no volume rather than zero. Coverage per ecosystem is documented in supported ecosystems.
- Where a signal is unavailable in a report — an uncollected dependency graph, an inconclusive Scorecard check, a report predating a signal — the repository is excluded from that figure's basis, never counted against it.
- Health indices are signals of publicly visible practice, not audits or warranties — how to read them is covered by the health index.
- Figures computed 2026-09-11 07:30 UTC; the aggregate is recomputed hourly. The underlying data is available as JSON.