Repowise · Codebase intelligence
kaizakin / siphon
Production-inspired Event Ingestion and Notification system
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 7 (35%) actually needed a bug fix in the last 6 months — 1.5× better than picking files at random.
Code health
Full report- Code health90
- Dead code70
- Hotspot density60
- Bus factor0
How kaizakin/siphon works
Production-inspired Event Ingestion and Notification system This page is an auto-generated, always-fresh map of the kaizakin/siphon 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 30 source files, 73 symbols, and 5 languages. Git churn analysis flags 6 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 14 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.