Record in aggregate · metrics 2.10.0

The state of Go.

Aggregate statistics across every inspected repository publishing to Go — how health distributes, where the download volume sits, and which practices are common or rare, measured against the whole record.

Inspected repositories
28,097 of 28,098 indexed
Monthly downloads under inspection
1.5B registry-reported
Median health index
53 Moderate
Good or better
31% index 65 and above

Health-index distribution

Latest health index of every inspected repository, in five-point intervals over the 1–100 scale.

Where the download volume sits

Combined monthly downloads by band, against repository counts.

22% of the monthly download volume under inspection flows through repositories below the good band — and the top 1% most-downloaded repositories carry 100% of the entire volume.

Repositories
24%21%18%
Download volume
26%46%
BandRepositoriesDownloads / moVolume share
Exceptional971378M26%
Excellent3,23487.3M6.0%
Good4,458680M46%
Moderate6,807204M14%
Weak6,0195.4M0.4%
At Risk5,02077.9M5.3%
Critical1,58832.1M2.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.

Vitality67
1100
Community & Adoption27
1100
Sustainability & Governance52
1100
Engineering Quality62
1100
Security44
1100
AI Readiness65
1100

Category profile

Median category score across the scope. Ticks mark the whole-record median. Categories are documented in the methodology wiki.

Vitality
67
Community & Adoption
27
Sustainability & Governance
52
Engineering Quality
62
Security
44
AI Readinessunweighted
65

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

Automated tests
91% of 28,097
README
88% of 28,097
License detected
88% of 28,097
CI workflows
77% of 28,097
Documentation directory
40% of 28,097
Linter configuration
40% of 28,097
Contributing guide
28% of 28,097
Security policy
18% of 28,097
Code of conduct
16% of 28,097

Agent-era signals

One-command bootstrap
54% of 28,097
AI agent instructions
28% of 28,097
llms.txt
12% of 28,097

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

Under 100 stars 24,296
50 · 34–63
100 – 999 2,373
78 · 62–89
1,000 – 9,999 1,136
86 · 69–94
10,000 and more 292
94 · 87–97

By monthly downloads

Under 10K / month 773
63 · 53–75
10K – 1M 192
83 · 69–90
1M – 100M 70
86 · 59–94
100M and more 1
71 · 71–71

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.

CII-Best-Practices
0.1
Branch-Protection
1.0
Fuzzing
1.1
Signed-Releases
1.1
Code-Review
1.6
SAST
1.7
Token-Permissions
2.1
Pinned-Dependencies
2.2
Security-Policy
2.3
Dependency-Update-Tool
3.9
Contributors
4.4
Maintained
5.1
Vulnerabilities
5.3
CI-Tests
7.1
License
8.7
Binary-Artifacts
9.8
Dangerous-Workflow
9.8
Packaging
10.0

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.

Abandonment
1,8456.6% of the record · 6.6% of 28,098 assessed
High-risk jurisdiction exposure
5682.0% of the record · 2.5% of 22,428 assessed
Malicious dependencies
7<0.1% of the record · <0.1% of 13,783 assessed
Inorganic growth
00% of the record · 0% of 145 assessed

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 17 days of inspection.

Push recency
58%30%
Last pushRepositoriesShare
Pushed within 30 days16,29658%
31 – 90 days8,44330%
91 – 365 days1,5685.6%
Over a year1,7906.4%

Stewardship & resilience

Who stands behind the inspected repositories, and how many people the code depends on. Both are read by the governance category.

13,549Organization-stewarded median 62
14,548Personal accounts median 45

Maintainer bus factor

84% of inspected repositories depend on a single maintainer for the majority of their commits — including 23 with over a million monthly downloads.

1 maintainer
23,146
2 maintainers
2,590
3–5 maintainers
1,527
6+ maintainers
329

The dependency iceberg

Declared direct dependencies against the full resolved graph (direct plus transitive), across the 14,859 reports with a collected dependency graph.

The median repository declares 7 direct dependencies — and resolves to 38 packages in total.

Resolved packages per repository

0
1,278
1 – 5
1,986
6 – 20
2,568
21 – 50
2,329
51 – 200
3,856
201 – 500
1,560
501 – 1,000
688
Over 1,000
594

License landscape

The most common detected licenses across the scope (SPDX identifiers).

MIT
11,977
Apache-2.0
7,498
No license detected
3,506
Custom license
1,662
GPL-3.0
738
BSD-3-Clause
730
AGPL-3.0
662
MPL-2.0
648
BSD-2-Clause
211
LGPL-3.0
87

Most relied upon

The most-downloaded repositories under inspection publishing to Go — the records the figures above weigh heaviest. The rest is covered by the full catalogue · tag index.

npm · Go
71Goodhealth index
WebReflection/flatted
A fast and minimal circular JSON parser.
JavaScript · Go · PHP★ 1,156↓ 583M/moSep 16, 2026
ISCSep 16, 2026 · metrics 2.10.0
PyPI · npm · Go
94Exceptionalhealth index
modal-labs/modal-client
SDK libraries for Modal
Python · Go · TypeScript★ 511↓ 82.6M/moAug 27, 2026
Apache-2.0Aug 27, 2026 · metrics 2.10.0
PyPI · npm · crates.io +1
62Moderatehealth index
tree-sitter/tree-sitter-bash
Bash grammar for tree-sitter
C · JavaScript★ 327↓ 41.4M/moAug 27, 2026
MITAug 27, 2026 · metrics 2.10.0
npm · Packagist · Maven +2
34At Riskhealth index
google/flatbuffers
FlatBuffers: Memory Efficient Serialization Library
C++ · Rust★ 26.5K↓ 32.8M/moSep 16, 2026
Apache-2.0Sep 16, 2026 · metrics 2.10.0
npm · PyPI · Packagist +4
96Exceptionalhealth index
cucumber/gherkin
A parser and compiler for the Gherkin language.
C★ 400↓ 32.5M/moAug 27, 2026
MITAug 27, 2026 · metrics 2.10.0
PyPI · npm · crates.io +1
63Moderatehealth index
tree-sitter/tree-sitter-javascript
Javascript grammar for tree-sitter
JavaScript · C · Tree-sitter Query★ 492↓ 32.5M/moAug 27, 2026
MITAug 27, 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-21 09:48 UTC; the aggregate is recomputed hourly. The underlying data is available as JSON.