Code health
This codebase scores 6.7 out of 10 for code health, which we rate fair. It also scores maintainability 7.5 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: 78 of 7,338 files are git hotspots, and they average 3.2 — which is where the fixes pay off most.
3 things worth doing this quarter.
Update the decision “Do not bound schema structural size at loader layer”: the code it governs has moved on
Agents and reviewers still follow it, so they are steered by a rule the code no longer keeps.
Update the decision “Reject pure $ref cycles but not mixed validation cycles”: the code it governs has moved on
Agents and reviewers still follow it, so they are steered by a rule the code no longer keeps.
Delete 260 unused symbols and files (2,288 lines)
Nothing in the graph reaches them, across 139 files; every reader and agent pays to skip them.
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.