Code health
This codebase scores 6.2 out of 10 for code health, which we rate fair. It also scores maintainability 7.4 and static performance 9.9 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 6 of 237 files are git hotspots, and they average 2.9 — which is where the fixes pay off most.
4 things worth doing this quarter.
Break up Layout (CCN 41, 152 lines)
layout/flex.go:182
Layout nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 48 files import it.
Break up windowProc (CCN 64, 231 lines)
app/os_windows.go:297
windowProc nests its control flow deeply; 2 files import it, changed 13 times in 90 days.
Delete 110 unused symbols and files (965 lines)
Nothing in the graph reaches them, across 30 files; every reader and agent pays to skip them.
Flatten the nesting in collect
io/input/router.go:789
collect nests its control flow deeply; 22 files import it, changed 2 times in 90 days.
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
Every detector's open count by area, each with its worst example. An inventory, not a to-do list: the actions above are the part worth doing.