Code health
This codebase scores 6.6 out of 10 for code health, which we rate fair. It also scores maintainability 6.7 and static performance 9.6 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 160 of 1,643 files are git hotspots, and they average 4.1 — which is where the fixes pay off most.
2 things worth doing in the week to Oct 1, the last indexed commit, 2 of them now.
Clean up what this week's commits left: 42 serious findings in 14 files
7 commits in the last 7 days added or worsened them, and they are still open. Start with backend/app/services/hitl_service.py, which has 4 critical.
Start breaking up execute (CCN 44, 190 lines): first lift lines 169-188
backend/app/services/node_execution/nodes/llm_node.py:169
execute nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 3 files import it, changed 5 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.