Code health
This codebase scores 6.3 out of 10 for code health, which we rate fair. It also scores maintainability 6.6 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: 145 of 768 files are git hotspots, and they average 4.7 — which is where the fixes pay off most.
4 things worth doing in the week to Sep 24, the last indexed commit, 4 of them now.
Clean up what this week's commits left: 32 serious findings in 13 files
14 commits in the last 7 days added or worsened them, and they are still open. Start with coworker/engine.py, which has 3 critical.
Start breaking up ProviderForm (CCN 65, 232 lines): first lift lines 452-462
surfaces/gui/src/providers/ProviderSetup.tsx:452
ProviderForm is long, branchy and widely depended on, and part of it is duplicated, so splitting it also removes a copy; 4 files import it, changed 14 times in 90 days.
Start breaking up ConnectorGlance (CCN 117, 330 lines): first lift lines 159-187
surfaces/gui/src/components/connectors/ConnectorGlance.tsx:159
ConnectorGlance is long, and part of it is duplicated, so splitting it also removes a copy; 1 file imports it, changed 1 time in 90 days.
Extract lines 396-411 of stream into a helper (+3 more steps)
coworker/providers/openai_provider.py:396
stream is complex and keeps changing, and part of it is duplicated, so splitting it also removes a copy; 10 files import it, changed 11 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.