[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2odw2khacazwf":3},{"code":4,"message":5,"data":6,"timestamp":46},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":42,"homepage":43,"updated_at":44,"history":45},"harry0703\u002FMangoDisk",10,"Safety-first disk cleaner and space analyzer for macOS, Windows and Linux, with duplicate cleanup, app uninstall, startup management, system optimization, and maintenance.","Rust",4770,326,546,85,[],"A cross-platform disk cleaner and space analyzer for people who want to reclaim storage without hand-auditing folders.","MangoDisk is worth a look if you regularly run low on disk space on macOS, Windows or Linux and want one tool that scans caches, large files and duplicates rather than clicking through each location yourself. The caveat is that cleanup tools must be judged by what they exclude and how you can preview, not by the size of the number they show.\n\n## The problem\n\nStorage fills up across system caches, browser data, app leftovers and build artifacts, and the usual workflow is to hunt through hidden folders, guess which files are safe to remove, and then repeat the process next month. MangoDisk replaces that with a scan that groups reclaimable content by location and size, plus a file explorer view of what is taking up space. The cleanup step is where the project changes the workflow: results come pre-selected with recommendations, and you review before applying. You end up with freed space and a clearer picture of where it went, not just a one-off deletion.\n\n## What's different\n\nThe mechanism is a Rust core with a Tauri 2 desktop shell, available for all three major desktop systems, and a `mangodisk` command-line interface that exposes the same scan and recommendation logic. By default `mangodisk clean` only scans and changes nothing; applying changes requires `--apply`, and non-interactive cleanup additionally requires `--yes`. A `--dry-run` with `--selection all` previews every selectable item, and `--format json` produces machine-readable output for scripts or review. That split between scanning, previewing and applying is the most useful design decision for anyone nervous about a cleaner deleting the wrong thing.\n\nThe trade-off is scope and selection policy. Smart selection keeps at least one file in every duplicate group and handles potential personal files cautiously during uninstall, but those policies are the author's choices, not guarantees about every system's layout. The tool also bundles privacy cleanup (browsing history, cookies, clipboard and recent items), application uninstall with leftover removal, startup management and resource monitoring. That breadth means the safety of a run depends on reviewing grouped results rather than trusting a total, and the README does not establish exactly how each category is classified.\n\n## Who should try it\n\nA good fit is a developer or power user on a laptop with limited storage who wants one scan covering caches, large installers, duplicate downloads and app leftovers, and who values the CLI's dry-run and JSON modes for checking results before applying them. It is also reasonable for someone who wants a graphical treemap or sunburst view to find the folders behind a full disk. A poor fit is someone who wants a single button that deletes everything without review, or who needs a tightly audited, minimal-footprint utility: the feature set is broad, and the README's descriptions of cautious handling are claims about selection logic rather than evidence of testing on your specific applications.\n\n## Requirements and limitations\n\nIt is a desktop application, so the main path is installing a release build for macOS, Windows or Linux; the CLI is part of the same project and is the better path for headless or scripted review. The README documents building the desktop installer from source with the Tauri toolchain, so source builds require that setup, while normal use is meant to go through releases. The project is GPL-3.0, which matters if you plan to modify and redistribute it.\n\nThe main ongoing care is reviewing what each scan selects, especially for application caches and uninstall leftovers where personal files could be adjacent. The README describes safeguards such as keeping one file per duplicate group, but it does not document a full recovery path for every deletion. Treat the preview modes as the place to decide, and verify on a non-critical machine or with backups before relying on broad cleanup.\n\n## HotRepo's take\n\nHotRepo began tracking this repository on 2026-10-24, and the only stored signal is a Rust weekly board position of #10 with +546 stars for the week of 2026-10-25. That single dated snapshot shows attention, but there is no daily-board history, so persistence cannot yet be judged. Before adopting it, check the release notes and scan the categories your workflow depends on—especially app leftovers and privacy cleanup—to confirm the selection policy matches what you consider safe to remove.\n\n[Project source and documentation](https:\u002F\u002Fgithub.com\u002Fharry0703\u002FMangoDisk)",{"slug":19,"name":20},"productivity","Productivity & Utilities",[22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"app-uninstaller","cache-cleaner","cross-platform","desktop-app","disk-cleaner","disk-cleanup","disk-space-analyzer","duplicate-files","duplicate-finder","large-files","linux","macos","rust","startup-manager","system-cleaner","system-optimization","tauri","treemap","uninstaller","windows","GPL-3.0","https:\u002F\u002Fmangodisk.app\u002F","2026-10-25T12:17:16Z",[],1792968284]