Discofork
Repository brief

exelban/stats

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-30T19:53:24.040Z
1mo ago

exelban/stats

Stats is a mature, actively maintained macOS menu bar system monitor with 37k+ stars and 1.2k+ forks. It targets users who want quick at-a-glance hardware and system metrics, and the repo shows ongoing releases and fixes as of 2026-03-30. Forks are most likely interesting if you care about macOS monitoring, menu bar UI work, device/sensor support, or localization-heavy maintenance.

GitHub
Loading tags...
Stars37,474
Forks1,235
Default branchmaster
Last pushed2026-03-30T17:05:13Z
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

Choose this fork if older macOS compatibility and custom build/release packaging matter more than staying current with upstream. If you want the newest fixes and hardware support, upstream is the safer choice.

Prefer upstream for normal use. This fork has no added value over upstream and is materially behind it, so it only makes sense as a frozen baseline or if you intend to do your own maintenance.

Prefer upstream unless you explicitly want this fork's older custom UI/behavior changes or want to salvage a few deleted/rewritten modules. For normal adoption, the stale base and major divergence make this a risky choice.

Choose this fork only if you want the older customized UI and process-list controls. For most adopters, upstream is the better choice because it is far more current, actively maintained, and likely more compatible with modern macOS and hardware.

Adopt this fork only if you want a very close upstream mirror; otherwise, upstream itself is the better choice because this fork adds nothing and is already one commit behind.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no visible capabilities and is behind on several recent fixes, so it is a worse default choice for most adopters.

Prefer upstream unless you specifically need this older baseline. This fork adds nothing concrete and is behind on several user-facing fixes and hardware updates.

Choose this fork if you need a customized Stats build for your own distribution or signing setup and value the extra process-count option. Choose upstream if you want the latest fixes, sensor/device improvements, and lower maintenance risk.

Choose this fork only if you specifically want an upstream snapshot. For most adopters, the original project is the better default because this fork shows no added features and is 51 commits behind.

Prefer upstream unless you explicitly want a frozen baseline or your own fork target. This fork offers no added features and is materially behind on maintenance, so it is not a better end-user choice than upstream.