Repowise · Codebase intelligence
anynines / klutchio
Automating dataservice lifecycles on Kubernetes — from provisioning to backup and restore.
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 2 (10%) actually needed a bug fix in the last 6 months — 1.4× better than picking files at random.
Languages
- go56.9%
- yaml33.1%
- shell4.6%
- markdown3.9%
- makefile0.7%
- dockerfile0.7%
- toml0.2%
Key modules4
- go
bind
bind
- go
a9s-backup-manager
clients/a9s-backup-manager
- go
a9s-open-service-broker
clients/a9s-open-service-broker
- go
provider-anynines
provider-anynines
Code health
How anynines/klutchio works
Automating dataservice lifecycles on Kubernetes — from provisioning to backup and restore. This page is an auto-generated, always-fresh map of the anynines/klutchio 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 613 source files, 2,682 symbols, and 7 languages, structured as a monorepo with 4 packages. Git churn analysis flags 7 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 252 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.