of contributions occurred in private repositories
GitHub’s dataset shows most day-to-day organizational development happens privately.
GitHub Octoverse 2025 · 2025 ↗Updated 2026-10-04 · Software delivery
A source-first view of exposure, attack paths and the speed at which material findings are closed. Published findings provide context; the measurement framework shows what to calculate inside your own environment.
01 / Published evidence
Each figure links directly to the organization that published it. Vendor telemetry and community surveys are labelled rather than blended into one invented industry average.
GitHub’s dataset shows most day-to-day organizational development happens privately.
GitHub Octoverse 2025 · 2025 ↗Verizon says vulnerability exploitation became the leading breach entry point in its 2026 DBIR.
Verizon 2026 DBIR announcement · 2026 ↗DORA combined this survey with more than 100 hours of qualitative research.
DORA 2025 report announcement · 2025 ↗02 / Your baseline
Use these formulas consistently for at least one complete operating cycle. Keep scope, exclusions and collection dates beside the result.
Open critical exposures ÷ 100 in-scope assets
Median days from validated finding to verified closure
Reopened or recurring findings ÷ all closed findings × 100
03 / Interpretation
Segment results by environment, workload owner and business criticality. A falling average can hide one critical service getting worse; a rising count can simply reflect better discovery.
Related benchmarks
Gritt can map the data sources, calculate a defensible baseline and implement the changes behind it.
Build the baseline →