Repowise · Codebase intelligence
bestseller / harpocrates
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 9 (45%) actually needed a bug fix in the last 6 months — 2.9× better than picking files at random.
Code health
Full report- Code health85
- Dead code92
- Hotspot density97
- Bus factor63
How bestseller/harpocrates works
This page is an auto-generated, always-fresh map of the bestseller/harpocrates repository, written primarily in Go. 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 71 source files, 232 symbols, and 5 languages. Git churn analysis flags 1 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 26 tightly-coupled module communities.
Use the panels 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.