H.10.6 Repository Metrics

Repository health is a portfolio of workflow outcomes, not repository size or one universal score.

• Measure time to first useful change, local and CI feedback, review wait, integration delay, recovery, repeated support, and platform toil.
• Segment results by workflow, language, platform, team, region, change class, and cold or warm state before drawing conclusions.
• Combine behavioral evidence with developer-reported friction; neither utilization nor sentiment alone explains the system.
• State telemetry purpose, access, retention, aggregation, and privacy limits, especially for developer-level data.
• Use metrics to test a decision and expose transferred cost, not to rank individuals or manufacture one repository-health number.