Code health
This codebase scores 5.9 out of 10 for code health, which we rate fair. It also scores maintainability 7.7 and static performance 9.7 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 47 of 352 files are git hotspots, and they average 3.7 — which is where the fixes pay off most.
4 things worth doing this quarter.
Break up load_config (CCN 13, 60 lines)
src/config/mod.rs:167
load_config nests its control flow deeply; 36 files import it, changed 11 times in 90 days.
Flatten the nesting in plan
src/autoplay/majsoul/mod.rs:48
plan nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 7 files import it, changed 20 times in 90 days.
Delete 35 unused symbols and files (705 lines)
Nothing in the graph reaches them, across 18 files; every reader and agent pays to skip them.
Break up aggregate (CCN 50, 264 lines)
src/history/aggregator.rs:102
aggregate nests its control flow deeply; 5 files import it, changed 4 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.