Code health of docker/compose
Repowise scores docker/compose at 6.2 out of 10 for code health, which reads as fair, alongside maintainability 7.7 and static performance 9.8 on the same scale. There are 924 open findings across the three pillars, and the lowest-scoring file is pull.go at 1.0. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.
Findings by severity
60 critical, 115 high, 251 medium, 468 low.
Hotspots
21 files are flagged as hotspots. The top 5:
- pkg/compose/reconcile_test.go: 7 commits in the last 90 days from 2 contributors with 2 recent bug fixes
- pkg/compose/reconcile.go: 12 commits in the last 90 days from 2 contributors with 3 recent bug fixes
- pkg/compose/convergence.go: 6 commits in the last 90 days from 18 contributors with 3 recent bug fixes
- pkg/compose/executor.go: 8 commits in the last 90 days from 2 contributors with 1 recent bug fix
- pkg/compose/publish.go: 3 commits in the last 90 days from 11 contributors with 4 recent bug fixes
Lowest-scoring files
- pkg/compose/pull.go: 1.0 out of 10 with 1 bug fix in the last 180 days
- pkg/compose/build_bake.go: 1.0 out of 10 with 3 bug fixes in the last 180 days
- pkg/compose/build_classic.go: 1.0 out of 10
- cmd/compose/config.go: 1.1 out of 10
- cmd/compose/compose.go: 1.8 out of 10 with 4 bug fixes in the last 180 days
Checked against bug fixes
Of the 20 files Repowise scores lowest, 16 had a bug fix in the last 180 days. Across all 383 scored files, 17.5% had a bug fix in that window.
Dead code and refactoring
Repowise found 40 unused exports.
More on compose: summary and FAQ, codebase overview, architecture.
Related guide: Best dead code detection tools by language