Stale Complex
Tier 2stale_complex High structural complexity but untouched for a long time. The risk is latent: when this code is next changed, the developer faces high complexity with no recent context. Refactor before the next development push.
parcel's compiler core carries the highest structural debt — 5 functions to fix first
The riskiest code in parcel-bundler/parcel isn't on fire right now — it's a slow-burning fuse. Five critical-band functions in the Rust compiler core have sat untouched for 239 days, each carrying enough structural complexity that the next developer to modify any of them faces a high probability of introducing a regression.
elysiajs/elysia's core index carries the highest activity risk — 5 functions to address first
Across 282 functions in elysiajs/elysia, I found 12 in the 'fire' quadrant — structurally complex and actively changing right now — with the worst concentrated inside a single file. If you're shipping code against this repo this week, `src/index.ts` is where regressions are most likely to originate.
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.
yarn's PnP resolver carries the highest structural debt — 4 functions to address first
Four of the five highest-risk functions in yarnpkg/yarn live in a single file — `src/util/generate-pnp-map-api.tpl.js` — and none of them have been touched in nearly six years. That concentration of structural debt in one module means that when the PnP resolution layer is next opened for changes, the engineer doing the work will be navigating some of the most complex code in the repository.
koajs/koa's response layer carries the highest structural risk — 5 functions to address first
Koa's response pipeline is carrying the most structural weight: the respond function in lib/application.js has accumulated god-function complexity with 26 independent execution paths and hasn't been touched in over seven months — meaning the next change there arrives against a high-complexity backdrop with no recent test pressure. Meanwhile, the set function in lib/response.js was modified today, making it the only live regression risk in the repository right now.
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.
type-challenges' automation scripts carry the highest activity risk — 3 functions to address first
The riskiest code in type-challenges isn't the type puzzles — it's the automation layer. Three scripts with CC up to 27 and fan-out up to 25 carry deep structural debt that warrants refactoring before the next development push.
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.
dayjs's core formatter carries the highest structural debt — 5 functions to address first
dayjs's core format function has 38 independent execution paths and calls 13 distinct functions — structural debt that will bite hard the moment that code is touched again.
ChatTTS's scheduler carries the highest activity risk — 5 functions to address first
ChatTTS has 40 critical-band functions across 440 total, with its inference and scheduling layer accumulating structural debt that will bite hard the next time anyone opens those files.
cobra's completion subsystem carries the highest activity risk — 5 functions to address first
cobra's completion layer is its most structurally fragile subsystem — one function alone calls 39 distinct callees, making any future change there a high-blast-radius event.
qlib's init and model layer carry the highest structural risk — 5 to refactor first
qlib's highest-risk functions aren't being actively changed right now — they're structural debt accumulating blast radius. Five god functions with CC scores up to 58 are overdue for refactoring before