Examples¶
All examples below are generated from the Kubernetes repository — one of the largest open-source Go projects with 135k+ commits and thousands of contributors.
History Analyzers¶
Burndown¶
The burndown chart shows how code survives over time: each colored band represents code written in a specific period, and its height shows how many lines from that period are still present at each sample point.
How to interpret
- Stacked layers = code written in different time periods
- Bottom layers = oldest code still surviving
- Narrowing layers = code being deleted or rewritten
- Flat layers = stable code that rarely changes
See the Burndown analyzer docs for configuration options.
Couples¶
The couples chart visualizes co-change relationships between files — files that are frequently modified together in the same commits.
How to interpret
- Connected nodes = files frequently changed together
- Cluster density = tightly coupled modules
- Isolated nodes = independent components
See the Couples analyzer docs for configuration options.
File History¶
The file history chart shows the most frequently modified files across the repository's entire commit history.
How to interpret
- Tallest bars = most frequently changed files (hotspots)
- High churn files often benefit from refactoring or better test coverage
See the File History analyzer docs for configuration options.
Anomaly Detection¶
The anomaly chart detects unusual patterns in commit activity — spikes or drops that deviate significantly from the repository's normal rhythm.
How to interpret
- Red points = anomalous activity (unusually high or low)
- Blue line = normal commit activity trend
- Anomalies may indicate major refactors, releases, or team changes
See the Anomaly Detection analyzer docs for configuration options.
Imports (History)¶
The imports history chart tracks how import dependencies evolve over the repository's commit history.
Developers¶
The developer dashboard shows contributor activity, workload distribution, language expertise, and code churn across the project's history.
How to interpret
- Activity chart = commit frequency per developer over time
- Workload treemap = proportional contribution by developer
- Radar chart = language expertise across top contributors
- Code churn = lines added vs removed per time period
See the Developers analyzer docs for configuration options.
Sentiment¶
The sentiment chart shows the emotional tone of commit messages over the project's history, detecting periods of positive or negative developer sentiment.
How to interpret
- Positive values = constructive, positive commit messages
- Negative values = frustration, urgency, or negative sentiment
- Sudden drops = may indicate stressful periods or difficult bugs
See the Sentiment analyzer docs for configuration options.
Shotness¶
The shotness charts visualize function-level co-change patterns — which functions are frequently modified together across commits.
How to interpret
- Treemap = function-level change frequency (larger = more changes)
- Heatmap = co-change correlation between functions
- Bar chart = most frequently modified functions
See the Shotness analyzer docs for configuration options.
Typos¶
The typos chart detects potential typos and misspellings in identifiers across the codebase's commit history.
See the Typos analyzer docs for configuration options.
Quality¶
The quality charts track code quality metrics (complexity and Halstead volume) over the commit history, showing how code quality evolves.
How to interpret
- Complexity trend = how function complexity changes over time
- Halstead volume = information content evolution of the codebase
Static Analyzers¶
Complexity¶
The complexity charts show cyclomatic and cognitive complexity metrics for the most complex functions in the codebase.
How to interpret
- Cyclomatic complexity = number of linearly independent paths through the code
- Cognitive complexity = how difficult the code is for humans to understand
- Functions with high complexity are candidates for refactoring
See the Complexity analyzer docs for configuration options.
Halstead¶
The Halstead charts measure software complexity through operator/operand counting — effort, difficulty, and volume metrics.
How to interpret
- Effort = estimated mental effort to understand the code
- Difficulty = how error-prone the code is
- Volume = information content of the code
See the Halstead analyzer docs for configuration options.
Cohesion¶
The cohesion charts measure how well the methods within a class or struct relate to each other. Higher cohesion indicates better-designed components.
How to interpret
- Score of 1.0 = all methods use all fields (perfect cohesion)
- Score near 0 = methods don't share fields (low cohesion, consider splitting)
See the Cohesion analyzer docs for configuration options.
Comments¶
The comments charts analyze documentation coverage — comment density, lines of code, and documentation scores across the codebase.
How to interpret
- Documentation score = ratio of documented public symbols
- Lines of code = file sizes across the codebase
- Files with low scores and high LOC are documentation priorities
See the Comments analyzer docs for configuration options.
Imports (Static)¶
The static imports charts show the most used import packages and their categorization across the codebase.
How to interpret
- Usage count = how many files import each package
- Categories = standard library, internal, external dependencies
See the Imports analyzer docs for configuration options.