I built DiskSage because I was tired of guessing what was eating my disk space

Wait 5 sec.

Hey everyone 👋 I’ve been building DiskSage, an open-source disk analyzer designed for developer machines. Developer disks tend to fill up with Docker data, build artifacts, package caches, simulators, local models, dependencies, and other things that aren’t necessarily just “junk.” Tools like du and ncdu are great at answering: “What is using my disk space?” DiskSage is trying to answer the next question: “What is this, why is it here, and is it actually safe to remove?” Every finding includes evidence and a safety tier: Safe — regenerable caches and downloaded artifacts. Careful — removable, but may cause downloads, reindexing, or lost state. Expert — Docker/VM disks, models, and owner-managed data. Never automatically selected. Cleanup is also intentionally conservative: Scan → Review → Plan → Revalidate → Move to Trash If something changes between scanning and cleanup, DiskSage fails closed and leaves it untouched. Everything stays local, and systems like Docker remain responsible for cleaning their own internal state. GitHub: https://github.com/talaatmagdyx/DiskSage It’s still pre-release, so I’d love feedback from other developers: What developer-specific storage would you want a tool like this to understand automatically?   submitted by   /u/talaatmagdyx [link]   [comments]