Repowise · Codebase intelligence
docker / compose
Does the health score find the bugs?
Repowise ranks every file by predicted defect risk. Of the 20 files it flags as riskiest, 16 (80%) actually needed a bug fix in the last 6 months — 4.6× better than picking files at random.
Languages
- go67.6%
- yaml17.0%
- markdown14.4%
- dockerfile0.3%
- makefile0.3%
- terraform0.3%
- json
Code health
Full report- Code health69
- Dead code94
- Hotspot density89
- Bus factor78
How docker/compose works
This page is an auto-generated, always-fresh map of the docker/compose 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 383 source files, 2,008 symbols, and 7 languages. Git churn analysis flags 22 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 139 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.