CSZHK/CleanMyPc
active
significant_divergence
Selected Prefer this fork if you want a safer, more app-like Mac maintenance experience with explicit recovery/review workflows. Prefer upstream Mole if you want the latest cleanup coverage, the original CLI/TUI model, and lower divergence risk.
farion1231/Mole
stale
significant_divergence
Choose this fork if you want Mole with custom cleanup coverage and are comfortable owning divergence risk. Choose upstream if you want the newest fixes, broader current cleanup support, and lower maintenance uncertainty.
rohunvora/Mole
stale
significant_divergence
Choose this fork if you want a customized Mole with broader/reshaped maintenance workflows and can accept lagging upstream. Choose upstream if you want the newest cleanup targets, fixes, and stronger confidence from active maintenance.
BolajiOlajide/Mole
stale
significant_divergence
Prefer upstream unless you specifically need this older snapshot. This fork does not add functionality, and its 170-commit lag means adopters would be giving up newer cleanup coverage, bug fixes, and operational polish.
Choose this fork if you want Mole with stronger protection defaults and a more controlled cleanup experience. Choose upstream if you want the latest cleanup coverage, fixes, and the broadest maintained feature set.
sw3do/Mole
stale
significant_divergence
Prefer this fork if your priority is safer cleanup semantics and a more polished operator experience. Prefer upstream if you want the newest cleanup coverage, fixes, and broadest feature parity.
nining/mole
slowing
significant_divergence
Choose this fork only if you want a substantially rewritten Mole and are comfortable validating behavior yourself. If you want the safest path with current upstream features, protections, and release alignment, upstream is the better default.
app111/mole
stale
significant_divergence
Prefer this fork only if you want its customized cleanup and monitoring behavior more than upstream freshness and safety coverage. For most users, upstream looks safer and more complete; this fork fits adopters who are willing to accept divergence and possible regressions.
Adopt this only if you want Mole with essentially no fork-specific changes. It is a very shallow fork, but it is already behind upstream, so most users should prefer the main repository unless they specifically need this fork’s history or ownership boundary.
Choose this fork only if you want an upstream-aligned mirror and do not need the latest 4 upstream fixes or new cleanup targets. Otherwise, upstream is the better default.