kaizakin / siphon
Production-inspired Event Ingestion and Notification system
Code health
kaizakin/siphon scores 9.0 out of 10 on defect risk, which Repowise rates Excellent. Maintainability scores 9.8 out of 10. Static performance risk scores 10.0 out of 10. The three are scored separately and never blended into a single number. 6 of 30 files are git hotspots, the places where changes and bug fixes concentrate.
Full health report- Files
- 30
- Symbols
- 73
- Modules
- 13
- Doc pages
- 0
- Dead exports
- 10
Where the risk concentrates
All 6 hotspotsRanked by prior bug fixes and change frequency, mined from the full git history rather than from the code alone.
| File | Churn | Prior fixes | Maintainers | Commits 90d |
|---|---|---|---|---|
| ingestion_server.gointernal/ingestion/grpc | 89.3th %ile | 2 | 1bus factor 1 | 6 |
| handlers.gointernal/auth/handlers | 92.9th %ile | 1 | 1bus factor 1 | 10 |
| query.sql.gointernal/auth/sqlc |
Read more about kaizakin/siphon
- 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/kaizakin/siphon)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/kaizakin/siphon)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, organised into 13 modules, led by go, sql, yaml. Static analysis leaves 21 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.