MIT open-source Windows 10/11 cleaner + disk analyzer in C#/.NET 10 WPF with a 'provably safe' rule: finds what most cleaners miss (the live CapabilityAccessManager.db-wal 70-500GB bug, WSL2/Docker .vhdx compaction, DriverStore superseded GPU drivers, hiberfil.sys, restore points, search index, oversized Outlook data files), 60+ researched cleanup categories, SHA-256-verified duplicate finder (always keeps one copy), scheduled cleaning. Refusals by design: no registry cleaning, no browser passwords/history, no C:\Windows\Installer, no forced deletion of locked files. Recycle-Bin deletes + full audit log.
'Free, MIT-licensed, no ads, no telemetry, no Pro tier.'
Launched
earliest announcement post_date
Repo created
GitHub stars
34 (as of 2026-10-31)
First release
Domain registered
(bitbroom.app)
Last seen alive
Checks
Mechanical checks derived from the fields above. Each row is one fact; "not yet checked" means exactly that, not a failure. There is no composite score; read them together.
Track record
110 days ago
Source published
Not yet checked
Release signing
Not yet checked
Security contact
Not yet checked
Reproducible builds
Not yet checked
Telemetry
Not yet checked
Runs elevated
Not yet checked
Auto-update channel
Not yet checked
Recent activity
Last seen 60 days ago
Research notes
A bingo card that fills itself: the launch post opens 'Full disclosure: I'm the developer' and closes 'PS: not doing promotion, just wanted people to know about my products' - the literal trust_signal square, verbatim.
Real Windows-internals knowledge despite the AI authorship: calls out the actual KB fix (KB5095093) for the CapabilityAccessManager.db-wal growth bug, WSL vhdx shrink procedure, DriverStore semantics - the strongest technical pitch in the catalog.
Honesty-forward posture: 'why should I trust a random cleaner? Fair question: don't trust it, read the code and the audit log'; answers 'Probably safe???' heckle by clarifying 'provably'.
Build pipeline: repo -> same-hour v1.0.0 -> domain 2 days later -> launch post 2 days after that; 12 releases in 8 weeks then quiet since v1.2.6 (2026-09-04).
Author comes from the iOS jailbreak/sideload community (username IOS_HACKERJB, subs r/jailbreak r/sideloaded), which is also where he discusses building the whole thing with 'Fable 5' via Cursor.
Canonical CSV entry and earliest author promotion found; the bug-led title (500GB log-file bug) is the pitch.
Full disclosure: I'm the developer. — Intro cliche
Windows can quietly eat hundreds of GB — WSL disks that never shrink, DriverStore hoarding old GPU drivers, and the current 500 GB log-file bug — Problem statement
it must be impossible for it to delete something you care about — Trust signal
not doing promotion, just wanted people to know about my products — Trust signal
why should I trust a random cleaner? Fair question: don't trust it, read the code and the audit log — Trust signal
Free, MIT-licensed, no ads, no telemetry, no Pro tier. — Virtue