Repository Analyses
Nightly hotspot reports for popular open-source repositories. Each report ranks functions by activity-weighted risk — complexity × recent commit frequency — and labels the antipatterns driving the score.
gson's type resolution and parsing carry the highest structural risk — 5 functions to address first
Five critical functions in google/gson carry extreme structural complexity — and none are being actively refactored. When the next development push arrives, the blast radius will be wide.
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.
croc's core transfer layer carries the highest activity risk — 5 functions to address first
Four of croc's five riskiest functions are actively changing right now — and they all live in the same two files that orchestrate every file transfer. That's a live regression risk, not a backlog item
MediaCrawler's JS bundle dominates the top 5 hotspots — exclude to surface Python risk
Every top hotspot in MediaCrawler lives inside a single minified JS bundle — meaning the real Python risk profile is entirely hidden until that file is excluded from analysis.
hackathon-starter's auth and API layer carries the highest activity risk — 5 functions to address first
All five of hackathon-starter's top hotspots sit in the auth and API layer — and every single one is in the 'fire' quadrant, meaning complexity and active commits are colliding right now.
pretext's analysis core carries the highest activity risk — 5 functions to address first
Five functions in pretext's analysis and line-breaking core are both structurally extreme and actively changing right now — the highest-risk combination for regressions during ongoing development.
jadx's decompiler core carries the highest activity risk — 5 functions to address first
jadx has 795 critical-band functions, and its top five are all in the 'fire' quadrant — complex code that's actively changing. That combination is live regression risk, not future cleanup.
ink's output and keypress layers carry the highest risk — 4 functions to address first
ink's terminal output and keypress parsing are changing right now — and they're also the most structurally complex code in the repo. That's the combination that causes regressions.
conductor-oss/conductor's UI layer carries the highest activity risk — 5 functions to address first
conductor's biggest structural risk isn't in its Java core — it's in the UI layer, where actively-changing JSON utility functions carry cyclomatic complexity scores of 99 and 120, making them live reg
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.
filebrowser's frontend and HTTP layer carry the highest activity risk — 5 functions to address first
Five of filebrowser's most critical functions are complex AND actively changing simultaneously — the search API, file listing view, and config handler are live regression risks, not backlog items.
exo's benchmarking layer carries the highest activity risk — 5 functions to address first
exo has 191 critical functions out of 1,549 — and its highest-risk hotspot is a god-function with cyclomatic complexity of 93 that's actively changing right now, making it a live regression risk.
Preact's diff engine carries the highest activity risk — 3 functions to address first
Preact's virtual DOM differ is both its most structurally complex code and its most actively changed — a combination that makes every commit to src/diff/index.js a live regression risk right now.
paperclip's server layer carries the highest activity risk — 5 functions to address first
Two server files in paperclip are changing fast while carrying extreme structural complexity — the kind of combination that makes regressions nearly invisible until they're already in production.
Chat2DB's SQL processing layer carries the highest activity risk — 3 functions to address first
Chat2DB has 385 critical functions across 6,984 analyzed — and its SQL split processor alone carries a cyclomatic complexity of 58 with 38 distinct callees. Here's what to fix first.
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.
bubbletea's core runtime carries the highest activity risk — 3 functions to address first
Three functions in bubbletea's core runtime are both structurally complex and changing right now — making them live regression risks, not just cleanup items on a backlog.
ai-hedge-fund's frontend layer carries the highest activity risk — 3 files to address first
All five of ai-hedge-fund's top hotspots sit in the frontend layer — and every one is a god function flagged as structural debt with a blast radius waiting to be triggered.
drawdb's editor and SQL layer carry the highest activity risk — 5 functions to address first
drawdb's diagram editor hides a live regression risk: its ControlPanel component is both deeply complex and actively changing right now — CC 55, nesting depth 15, and 163 distinct callees.
gstack's browse layer carries the highest activity risk — 5 functions to address first
gstack's browse layer is under live regression pressure: its top command handlers combine extreme cyclomatic complexity with high recent commit activity, putting every active change at elevated risk.
learn-claude-code's agent layer carries highest activity risk — 5 functions to address
The agent loop functions in learn-claude-code are both structurally complex and actively changing right now — a combination that makes regressions easy to introduce and hard to catch.
get-shit-done's CLI core carries the highest activity risk — 5 functions to address first
Every top hotspot in get-shit-done lives in the CLI layer — and all five are actively changing right now. The command dispatcher alone has 181 execution paths and calls 108 distinct functions.
lx-music-desktop's renderer layer carries the highest structural risk — 5 functions to address first
183 critical functions in lx-music-desktop — and the riskiest ones sit untouched in the renderer layer, accumulating structural debt that will bite hard the next time anyone opens them.
bruno's OpenAPI sync and CLI runner carry the highest activity risk — 3 functions to address first
Two anonymous god-functions in openapi-sync.js (CC 135, CC 100) and a CLI runner function (CC 169) are both structurally extreme and actively changing, making them live regression risks in bruno's request execution layer.