Code health of betterleaks/betterleaks
Repowise scores betterleaks/betterleaks at 7.3 out of 10 for code health, which reads as good, alongside maintainability 8.1 and static performance 9.7 on the same scale. There are 720 open findings across the three pillars, and the lowest-scoring file is root.go at 2.0. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.
Findings by severity
46 critical, 131 high, 211 medium, 239 low.
Hotspots
54 files are flagged as hotspots. The top 5:
- detect/detect.go: 18 commits in the last 90 days from 6 contributors with 4 recent bug fixes
- detect/detect_test.go: 10 commits in the last 90 days from 4 contributors with 1 recent bug fix
- config/config.go: 4 commits in the last 90 days from 4 contributors with 3 recent bug fixes
- report/finding.go: 10 commits in the last 90 days from 4 contributors with 1 recent bug fix
- cmd/root.go: 11 commits in the last 90 days from 6 contributors with 2 recent bug fixes
Lowest-scoring files
- cmd/root.go: 2.0 out of 10 with 2 bug fixes in the last 180 days
- detect/utils.go: 2.2 out of 10 with 3 bug fixes in the last 180 days
- sources/files.go: 2.2 out of 10 with 1 bug fix in the last 180 days
- sources/file.go: 2.5 out of 10 with 2 bug fixes in the last 180 days
- detect/detect.go: 2.5 out of 10 with 4 bug fixes in the last 180 days
Checked against bug fixes
Of the 20 files Repowise scores lowest, 14 had a bug fix in the last 180 days. Across all 489 scored files, 7.2% had a bug fix in that window.
Dead code and refactoring
Repowise found 7 unused exports. 61 refactoring targets across 61 files would raise the score.
More on betterleaks: summary and FAQ, codebase overview, architecture.