Code health
This codebase scores 8.1 out of 10 for code health, which we rate good. It also scores maintainability 8.9 and static performance 9.8 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 498 of 5,591 files are git hotspots, and they average 6.0 — which is where the fixes pay off most.
4 things worth doing this quarter.
Flatten the nesting in deleteTeamResources
packages/omo-opencode/src/features/team-mode/team-runtime/delete-team.ts:150
deleteTeamResources nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 6 files import it, changed 4 times in 90 days.
Flatten the nesting in pollSessions
packages/omo-opencode/src/features/tmux-subagent/polling-manager.ts:127
pollSessions nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 4 files import it, changed 2 times in 90 days.
Delete 148 unused symbols and files (1,162 lines)
Nothing in the graph reaches them, across 100 files; every reader and agent pays to skip them.
Break up runTuiInstaller (CCN 45, 167 lines)
packages/omo-opencode/src/cli/tui-installer.ts:162
runTuiInstaller has many independent paths through it, and part of it is duplicated, so splitting it also removes a copy; 5 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.