Discofork
Repository brief

aristocratos/btop

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-31T09:49:43.279Z
1mo ago

aristocratos/btop

btop is an actively maintained system resource monitor with a large user base and a very active upstream: 31k stars, 958 forks, and commits as recent as 2026-03-23. It looks like a mature, cross-platform C++23 project with packaging, testing, and platform-specific build support already in place. Forks are most interesting if you care about a polished terminal system monitor, platform support work, theming/customization, or downstream distro/packaging changes.

GitHub
Loading tags...
Stars31,311
Forks958
Default branchmain
Last pushed2026-03-23T16:43:34Z
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 you specifically need DGX Spark/aarch64 GPU support or GCC 13 compatibility. Prefer upstream if you want the newest btop fixes and broader platform support.

Choose this fork if your priority is downstream build/packaging stability and you can tolerate lagging behind upstream. Choose upstream if you want the newest monitoring features, GPU support, and lower maintenance burden.

Choose upstream unless you specifically need this fork's older local tweaks. This fork looks like a stale, highly diverged snapshot suited to downstream pinning or niche patch maintenance, not everyday adoption.

Prefer upstream unless you specifically want this exact snapshot for local experimentation; it offers no clear added capability and is behind recent upstream work.

Prefer upstream unless you specifically need this fork as a local working copy; it adds no visible capabilities and is already behind recent upstream fixes and hardware support.

Prefer upstream unless you specifically need the fork's local filtering, theme, or collector changes and are prepared to maintain a long-lived divergent codebase yourself.

Choose this fork only if the extra `mise` installation documentation matches your workflow; otherwise upstream looks like the better default because this fork is essentially a docs-only variation.

Prefer upstream unless you specifically need this exact snapshot or plan to build private changes on top of it. As a user-facing fork, it does not yet add visible capabilities and is already behind recent upstream fixes.

Use this fork only if you specifically want a mostly untouched snapshot; otherwise upstream is the better choice because it is more current and this fork adds nothing visible.

Adopt this only if you want an unchanged snapshot to build on. For most users, upstream is the better choice because this fork adds nothing and lags 7 commits behind.