Health-index distribution
Latest health index of every inspected repository, in five-point intervals over the 1–100 scale.
median 71
Critical · 491At Risk · 1238Weak · 1123Moderate · 2710Good · 335136441478
Record in aggregate · metrics 2.10.0
The state of PyPI.
Aggregate statistics across every inspected repository publishing to PyPI — how health distributes, where the download volume sits, and which practices are common or rare, measured against the whole record.
Inspected repositories
14,035 of 14,036 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
98.2B 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
71 Good
The midpoint health index across the scope, computed under metrics 2.10.0.
Good or better
60% 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.
18% of the monthly download volume under inspection flows through repositories below the good band — and the top 1% most-downloaded repositories carry 66% of the entire volume.
Repositories
26%24%19%
Download volume
38%31%
| Band | Repositories | Downloads / mo | Volume share |
|---|---|---|---|
| Exceptional | 1,478 | 37.5B | 38% |
| Excellent | 3,644 | 30.2B | 31% |
| Good | 3,351 | 12.7B | 13% |
| Moderate | 2,710 | 8.5B | 8.7% |
| Weak | 1,123 | 1.9B | 1.9% |
| At Risk | 1,238 | 5.9B | 6.0% |
| Critical | 491 | 1.5B | 1.5% |
Score shapes
The distribution behind each category median, in ten-point bins — where the record clusters, and where a category separates repositories or saturates.
Vitality75
1100
Community & Adoption54
1100
Sustainability & Governance60
1100
Engineering Quality78
1100
Security54
1100
AI Readiness60
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 3 days of inspection.
Push recency
72%
| Last push | Repositories | Share |
|---|---|---|
| Pushed within 30 days | 10,149 | 72% |
| 31 – 90 days | 1,618 | 12% |
| 91 – 365 days | 1,011 | 7.2% |
| Over a year | 1,257 | 9.0% |
Stewardship & resilience
Who stands behind the inspected repositories, and how many people the code depends on. Both are read by the governance category.
8,225Organization-stewarded median 78
5,810Personal accounts median 62
Maintainer bus factor
74% of inspected repositories depend on a single maintainer for the majority of their commits — including 1,299 with over a million monthly downloads.
The dependency iceberg
Declared direct dependencies against the full resolved graph (direct plus transitive), across the 10,541 reports with a collected dependency graph.
The median repository declares 3 direct dependencies — and resolves to 30 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 PyPI — the records the figures above weigh heaviest. The rest is covered by the full catalogue · tag index.
PyPI
urllib3/urllib3
urllib3 is a user-friendly HTTP client library for Python
MITAug 28, 2026 · metrics 2.10.0
PyPI
pypa/packaging
Core utilities for Python packages
Custom licenseSep 16, 2026 · metrics 2.10.0
PyPI
kjd/idna
Internationalized Domain Names for Python (IDNA 2008 and UTS #46)
BSD-3-ClauseSep 16, 2026 · metrics 2.10.0
PyPI
python/typing_extensions
Backported and experimental type hints for Python
Custom licenseOct 23, 2026 · metrics 2.10.0
PyPI
psf/requests
A simple, yet elegant, HTTP library.
Apache-2.0Sep 16, 2026 · metrics 2.10.0
PyPI
certifi/python-certifi
(Python Distribution) A carefully curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts.
Custom licenseOct 23, 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-10-24 09:33 UTC; the aggregate is recomputed hourly. The underlying data is available as JSON.