Code health
KGerring/metrics scores 8.5 out of 10 on defect risk, which Repowise rates Excellent. Maintainability scores 8.8 out of 10. Static performance risk scores 9.6 out of 10. The three are scored separately and never blended into a single number.
Full health report- Files
- 521
- Symbols
- 730
- Modules
- 44
- Doc pages
- 0
- Dead exports
- 0
Read more about KGerring/metrics
- OverviewFiles, symbols, languages, packages, git intelligence
- ArchitectureDependency graph, layered architecture, symbol index, and third-party dependencies
- Code healthPer-file health scores, hotspots, test coverage, dead code, and refactoring targets
- AI explanationsProModule-by-module documentation generated from source
Add a badge to your README
Both badges are public, cached, and update on their own after every index. Nothing to install.
Repowise badge
Links to this page. Adding it also re-indexes the repo every week.
[](https://repowise.dev/repo/KGerring/metrics)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/KGerring/metrics)How KGerring/metrics works
This page is an auto-generated, always-fresh map of the KGerring/metrics repository, written primarily in yaml. Repowise indexes the source, parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 521 source files, 730 symbols, and 8 languages, organised into 44 modules, led by yaml, javascript, markdown. Static analysis leaves 576 open findings across the three health dimensions.
Use the links above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.