Git & Version Control
Git Blame Age Calculator
Enter file last modified date, author count, and line count to compute code age, bus factor risk, and maintenance risk score.
No data is transmitted — everything runs locallyTool
Example — A medium-size file last changed in mid-2023 with three authors for maintainability review.
Code age
33.8 months
1014 days since last change
Authors
3
Medium bus factor risk
Lines
450
in this file
Recommendation
Monitor
About this tool
Git Blame Age Calculator
The Git Blame Age Calculator computes code age, bus factor risk from author concentration, and maintenance risk score from blame statistics.
• Assess bus factor risk for a critical module before a team member leaves
• Calculate code age for a maintenance risk assessment
• Identify stale high-complexity files for a refactoring prioritization
• Build data for an engineering health dashboard
Affiliate disclosure
Uptime, incident, and on-call management. Better Stack provides status pages, incident management, and on-call scheduling for engineering teams.
View options with Better Stack
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The Git Blame Age Calculator computes code age, bus factor risk from author concentration, and maintenance risk score from blame statistics.
What affects the result most?
Code age = today - last_modified_date for a line or file. High churn + old age: code modified frequently then abandoned — risk signal. Knowledge concentration: if one author owns >80% of recent blame, bus factor = 1.
How should I use the result?
The calculation is deterministic — the same inputs always produce the same output — so the most useful workflow is to vary one input at a time and see which factor moves the result most. That tells you where to focus your attention before committing to a decision.