/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

tw93/Mole

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-30T11:51:53.970Z

3mo ago

tw93/Mole

Mole is an actively maintained Go-based macOS maintenance tool with a large user base and high fork activity. It focuses on deep cleaning, uninstalling apps and leftovers, disk analysis, system optimization, and live machine stats, all from a single binary. The repo is MIT-licensed, has 44,744 stars and 1,321 forks, and was last pushed on 2026-03-30.

Loading tags...

Stars44,744

Forks1,321

Default branchmain

Last pushed2026-03-30T03:05:15Z

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

Maintenance:

Magnitude:

Sort:

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.

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.

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.

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.

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.

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.

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.

Fork comparison

CSZHK/CleanMyPc

70/100

active

significant_divergence

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.

Likely purpose

To turn Mole from a Go CLI/TUI utility into a more guided, polished Mac maintenance product with safer cleanup evidence, a different UI stack, and a broader application/platform structure.

Best for

Mac users who want a guided maintenance app rather than a terminal-first utility.; People who value recovery-first, explainable cleanup over maximum breadth of low-level commands.; Teams or individuals who want to build a more polished consumer product on top of Mole's maintenance ideas.; Adopters who prefer a visually refined app and landing experience over a minimalist Go tool.

Additional features

Explainable, recovery-first cleanup flows with review-only uninstall evidence before destructive actions.
A new Swift application stack and supporting infrastructure instead of the original Go single-binary toolchain.
A redesigned landing site with glassmorphism styling and dark/light theme switching.
Container cleanup support and broader cleanup workflow packaging around the app experience.
More productized presentation focused on a compact 6.2 MB install package and streamlined onboarding.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

The fork is 124 commits behind upstream, so it likely misses some of Mole's newest cleanup fixes and feature additions.
Upstream's mature Go CLI/TUI single-binary workflow and command set may be less central here than in Mole.
Recent upstream safety/performance refinements may lag, including cleanup speedups, tighter cleanup scope fixes, and newer macOS compatibility fixes.
Upstream's latest bundled maintenance features such as newer specialized cleanup targets and status/optimization polish may not yet be present.
It trails upstream by 124 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Much stronger recovery and review posture for users worried about deleting the wrong files.
More polished, guided product surface than a plain terminal utility.
Broader app-oriented architecture may be easier to extend into a full maintenance suite.
The fork is still active and recently updated, not abandoned.

Risks

Large divergence from upstream makes future merges harder.
Being behind upstream means some bugfixes and cleanup coverage are likely stale.
A more complex Swift/app architecture can increase maintenance overhead versus the original single-binary design.
Users expecting Mole's CLI-first workflow may find this fork less direct.