Code health
This codebase scores 6.5 out of 10 for code health, which we rate fair. It also scores maintainability 7.8 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: 47 of 1,299 files are git hotspots, and they average 3.8 — which is where the fixes pay off most.
3 things worth doing this quarter.
Break up generateExpression (CCN 34, 167 lines)
src/webgl/strands_glslBackend.js:335
generateExpression nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 2 files import it, changed 2 times in 90 days.
Break up generateExpression (CCN 43, 199 lines)
src/webgpu/strands_wgslBackend.js:635
generateExpression nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 1 file imports it, changed 2 times in 90 days.
Start breaking up fesCore (CCN 73, 320 lines): first lift lines 36-602 into a helper
src/friendly_errors/fes_core.js:36
fesCore is complex and keeps changing, and part of it is duplicated, so splitting it also removes a copy; 1 file imports it, changed 3 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”.
Review the 14 proposed decisions
None is accepted yet, so nothing can drift from one and agents get no enforced guidance from them.
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.