rust Code Health
10 open-source rust repositories analyzed by activity-weighted risk — complexity × recent commit frequency. Sorted highest risk first.
agent-browser's React bridge has top activity risk — 5 functions to address first
A Hotspots analysis of vercel-labs/agent-browser at commit 82eadce, surfacing React instrumentation, CLI, and command-parser functions with the highest activity-weighted risk.
rustfs storage and protocol hotspots — 5 functions to address first
In rustfs, the highest-priority functions are not concentrated in one subsystem: storage healing, Swift request handling, scanner traversal, lifecycle evaluation, and object listing all appear in the top five. The common theme is structural density — every listed function combines complex branching, deep nesting, exit-heavy flow, god-function scope, and long-function shape.
rust-course's rustlings-zh entry points carry the highest structural debt — 2 functions to address first
The two highest-risk functions in rust-course haven't been touched in over three years — but their complexity means the next developer who does will face a steep blast radius.
zoxide's import layer carries the highest activity risk — 3 functions to address first
zoxide's import subsystem is live regression territory right now: two actively changing functions carry cyclomatic complexity of 16–19 while a utility god-function hasn't been touched in 606 days but carries a blast radius of 14 distinct callees.
casey/just's parser and lexer carry the highest activity risk — 5 functions to address first
just's parser and lexer are both deeply complex and under active development right now — a combination that puts live regressions well within reach as the codebase continues to evolve.
fuels-rs's docs theme carries the highest activity risk — 5 vendored functions to address first
Every one of fuels-rs's top 5 hotspots lives inside a single vendored file. The real Rust codebase deserves a closer look once that noise is filtered out.
lapce's command dispatch carries the highest activity risk — 3 functions to address first
A CC of 294 in a function that's actively changing right now isn't a backlog item — it's a live regression risk. lapce's command dispatch layer is where structural debt and commit churn collide.
iced's winit and widget layers carry the highest structural risk — 5 functions to address first
Two functions in iced's winit and widget layers carry extreme cyclomatic complexity — one topping CC 166 — making them the highest blast-radius targets before the next development push.
comprehensive-rust's theme layer carries the highest activity risk — 4 functions to address first
The riskiest code in google/comprehensive-rust isn't in the Rust source — it's in the JavaScript theme layer, where functions with fan-out as high as 72 are actively changing right now.
fd's walk and exec subsystems carry the highest structural risk — 5 functions
fd's walk and exec subsystems concentrate the most complex, high-blast-radius code in the codebase — 11 critical functions across 274 total, with structural debt that warrants attention before the nex