java Code Health

9 open-source java repositories analyzed by activity-weighted risk — complexity × recent commit frequency. Sorted highest risk first.

Repositories 9
Avg Top Risk 17.5
Top Patterns exit_heavydeeply_nestedcomplex_branching
alibaba/canal risk 18.7

alibaba/canal's adapters carry the highest activity risk — 5 functions to address first

A Hotspots analysis of alibaba/canal at commit cf97b2a, surfacing the top functions by activity-weighted risk score.

exit_heavygod_function
Read →
binarywang/WxJava risk 16.4

WxJava's member card and serialization layers carry the highest structural risk — 5 functions to address first

WxJava's highest-risk function has CC 42 and 72 callees, so the next developer to open it faces a high blast-radius change.

exit_heavygod_function
Read →
CodePhiliaX/Chat2DB

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.

cyclic_hubhub_function
Read →
conductor-oss/conductor

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

complex_branchingdeeply_nested
Read →
skylot/jadx

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.

complex_branchingdeeply_nested
Read →
google/gson

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.

exit_heavydeeply_nested
Read →
redisson/redisson

Redisson's cron layer carries the highest activity risk — 5 functions to address first

Redisson's cron scheduling and async batch execution layer is both structurally extreme and actively changing — a combination that makes every commit a live regression risk right now.

complex_branchingdeeply_nested
Read →
apache/rocketmq

RocketMQ's broker and client layers carry the highest activity risk — 5 functions to address first

RocketMQ's broker transaction checker and pop-revive service are both structurally complex and actively changing — a live regression risk hiding inside a high-throughput messaging core.

complex_branchingdeeply_nested
Read →
xuxueli/xxl-job

xxl-job's cron scheduler carries the highest activity risk — 2 functions to address first

xxl-job's cron parsing layer is its most urgent structural risk: two functions in CronExpression.java are both maximally complex and actively changing — a combination that makes every commit a potential regression

complex_branchingdeeply_nested
Read →

Other Languages