Code health
This codebase scores 5.4 out of 10 for code health, which we rate needs work. It also scores maintainability 6.1 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: 766 of 5,357 files are git hotspots, and they average 3.5 — which is where the fixes pay off most.
4 things worth doing this quarter.
Break up submit_order_list_command (CCN 24, 219 lines)
crates/adapters/polymarket/src/execution/orders.rs:554
submit_order_list_command nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 2 files import it, changed 10 times in 90 days.
Break up dispatch_ws_message (CCN 23, 107 lines)
crates/adapters/bitmex/src/websocket/dispatch.rs:270
dispatch_ws_message 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.
Delete 1,123 unused symbols and files (16,452 lines)
Nothing in the graph reaches them, across 78 files; every reader and agent pays to skip them.
Break up py_connect (CCN 41, 296 lines)
crates/adapters/kraken/src/python/websocket_spot.rs:440
py_connect nests its control flow deeply, and part of it is duplicated, so splitting it also removes a copy; 6 files import it, changed 9 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.