GitHub Metric
Engineering
Bug Fix Rate = Bugs Closed in Period / Total Open Bugs at Start of Period × 100
Bug Fix Rate measures the proportion of bug-labelled issues closed within a given period relative to the total number of open bugs. It reflects a team's capacity and prioritisation of quality work. A consistently low rate may signal under-investment in reliability.
GitHubEngineeringBug Fix Rate
Bug Fix Rate measures the proportion of bug-labelled issues closed within a given period relative to the total number of open bugs. It reflects a team's capacity and prioritisation of quality work. A consistently low rate may signal under-investment in reliability.
How to calculate bug fix rate
Why bug fix rate matters for GitHub users
Unresolved bugs erode user trust and compound over time, creating an ever-growing backlog that demoralises developers. A healthy bug fix rate signals that the team balances feature delivery with quality investment.
For GitHub-based teams, tracking this metric alongside new-bug inflow reveals whether the backlog is growing or shrinking. It also helps product managers make informed decisions about when to schedule dedicated quality sprints.
Understand and act on bug fix rate with KPI Tree
Sync GitHub issue data into your warehouse and create a bug fix rate metric in KPI Tree. Place it in a tree beneath customer satisfaction or product quality to visualise its downstream impact.
Assign ownership to the relevant squad lead and configure weekly alerts when the rate drops below your target threshold.
Get started with your GitHub data
MCPPull metrics from GitHub directly through the Model Context Protocol.
Connect your existing warehouse where GitHub data already lands.
Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.
Related GitHub metrics
Issue Resolution Time
EngineeringMetric Definition
Issue Resolution Time = Issue Closed Timestamp − Issue Created Timestamp
Issue Resolution Time measures the elapsed time from when a GitHub issue is opened to when it is closed. It reflects team responsiveness, prioritisation effectiveness, and overall execution speed. Segmenting by label (bug, feature, chore) provides more actionable insights.
Code Quality Trend Analysis
EngineeringMetric Definition
Code Quality Trend Analysis aggregates signals such as linting violations, cyclomatic complexity, code duplication, and static-analysis findings over time. It provides a longitudinal view of code health across repositories. Consistent improvement indicates maturing engineering practices.
Security Alert Resolution Time
EngineeringMetric Definition
Resolution Time = Alert Resolved Timestamp − Alert Created Timestamp
Security Alert Resolution Time measures the elapsed time from when a security alert (Dependabot, code scanning, or secret scanning) is opened to when it is resolved or dismissed in GitHub. It quantifies the organisation's responsiveness to known vulnerabilities and the effectiveness of its security remediation process.
Technical Debt Accumulation
EngineeringMetric Definition
Technical Debt Accumulation measures the rate at which technical debt grows across a codebase, using proxies such as TODO/FIXME comment count, aged open issues labelled as tech-debt, increasing cyclomatic complexity, and dependency staleness. Rising accumulation signals that short-term trade-offs are compounding into long-term burden.
All GitHub metrics
Branch Lifecycle AnalysisCode Churn RateCode Coverage TrendCode Quality Trend AnalysisCode Review Quality ScoreCode Review VelocityCommit FrequencyDeployment FrequencyDeveloper Contribution PatternsDeveloper Productivity ScoreDevOps Pipeline EfficiencyDiscussion Engagement RateFeature Development Cycle TimeIssue Resolution TimeLead Time for ChangesOpen Source Contribution AnalysisPull Request Approval RatePull Request Bottleneck AnalysisRelease VelocityRepository Health ScoreSecurity Alert Resolution TimeSecurity Vulnerability TrendsSprint Velocity TrackingTeam Collaboration IndexTechnical Debt AccumulationEmpower your team to understand and act on GitHub data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.
