Analyze contributor statistics with commit counts, code churn, and contribution patterns. Part of the DevTools Surf developer suite. Browse more tools in the DevOps / CI-CD collection.
Use Cases
Identify knowledge silos in a codebase before losing key team members
Analyze contribution patterns when evaluating an acquisition target's engineering team
Recognize top contributors for recognition or promotion decisions
Audit open-source project health before depending on it as a dependency
Tips
Paste git log --numstat output to get per-file change statistics with insertion and deletion counts per contributor
Use the 'bus factor' panel — it shows which contributors are the sole owners of significant portions of the codebase, indicating knowledge concentration risk
The contribution frequency chart reveals team velocity patterns; look for sustained decline to identify engagement or burnout signals
Fun Facts
The 'bus factor' (or 'truck factor') is defined as the minimum number of contributors that must be incapacitated before a project stalls. Most open-source projects have a bus factor of 1-2 — a surprisingly fragile state for critical infrastructure software.
A 2022 Linux Foundation study found that 10% of contributors to the Linux kernel are responsible for over 50% of commits. This core-contributor concentration is typical of successful open source projects despite having thousands of total contributors.
GitHub's Octoverse report in 2023 found that the average developer contributes to a median of 3 repositories per year. The most active 1% of GitHub users contribute to over 100 repositories annually.
FAQ
What is a healthy bus factor for a production codebase?
For critical systems, a bus factor of at least 3-5 is recommended. A bus factor of 1 means a single developer's departure or incapacitation could halt the project. Pair programming, code review, and documentation reduce single-contributor concentration.
Does commit count accurately measure contribution?
No — commit count varies by developer style (some make many small commits, others make few large ones) and favors tasks like configuration over complex algorithmic work. Lines of code added and reviewed, test coverage, and PR review activity are better multi-dimensional measures.
How do I export git statistics for analysis?
Use git log --numstat --pretty=format:'%an' to get author and file-level statistics. For GitHub repos, the Insights > Contributors tab shows monthly commit counts. The GitHub API provides programmatic access to contributor data.
