Discofork
Repository brief

alibaba/arthas

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T20:02:01.076Z
1mo ago

alibaba/arthas

Arthas is an actively maintained Apache-licensed Java diagnostics tool from Alibaba for troubleshooting production JVM applications without code changes or restarts. It is large and mature, with strong adoption signals (37k+ stars, 7.6k+ forks) and a recent release line at 4.1.8.

GitHub
Loading tags...
Stars37,217
Forks7,638
Default branchmaster
Last pushed2026-03-28T16:08:11Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork if your main need is richer, MVEL-driven command expression support inside Arthas. Prefer upstream if you want the latest maintained baseline, maximum compatibility, and the broadest set of current fixes.

Prefer this fork if you need a secured, service-oriented Arthas deployment with auto-discovery and added diagnostics UIs. Prefer upstream if you want the latest maintained line and lower upgrade risk.

Prefer upstream unless you specifically need this fork’s custom experimental workflows or are already committed to maintaining a legacy branch. For most adopters, the staleness and divergence outweigh the benefits.

Choose this fork only if your goal is a Gitee-syncing mirror. If you want the newest Arthas fixes or features, upstream is the better default because this fork is materially behind and adds only repository automation.

Prefer upstream unless you specifically need this frozen revision; this fork adds no new capability and is materially behind current Arthas.

Prefer upstream unless you specifically need the fork's translation work or the ability to skip telnet/HTTP port binding. For most adopters, this fork is too stale and diverged to be a good default choice.

Choose this fork if you want a readable, annotated Arthas codebase for learning or documentation. Choose upstream if you need an actively maintained production diagnostics tool with the latest features and fixes.

Prefer upstream unless you specifically need the fork's custom web, gRPC, JFR, or MCP-oriented experiments and can absorb the maintenance risk. For most adopters, the fork looks too stale and too divergent to be a safe default.

Choose this fork only if you specifically need its older custom diagnostics experiments. For most adopters, upstream Arthas is the better choice because it is actively maintained and much more complete.

Choose this fork only if you need its custom integration work and are prepared to own a long-lived maintenance branch. For most adopters, upstream Arthas is the safer and more capable choice because it is actively maintained and materially ahead.