Developer Tools & CLI Active CLI v0.1.0 2026 Dual: WaqfDPL-Mulzim 1.0 / AGPL-3.0

StorageAudit

Sub-second Linux workstation storage bloat auditor and surgical cleanup tool

Go CLILinuxZero TelemetryWaqf

The Problem

Why This Was Built

Modern developer workstations accumulate dozens of gigabytes of hidden build caches, browser offline storage, and stale dependencies, but standard Linux tools like du and df cannot distinguish disposable bloat from critical code or detect unlinked ghost files.

The Solution

The Architectural Answer

Delivers sub-second workstation storage triage across eight bloat categories, ranks candidates by age and reclaimable size, and performs surgical cleanups with strict safety boundaries and dry-run previews.

Capabilities

Key Features & Architecture

Sub-second multi-drive storage audit with inode meters and mount point capacity indicators

Eight bloat categories: compiler caches, package stores, stale git modules, browser storage, ghost files, runaway logs, superseded binaries, and desktop trash

Fail-closed safety invariants: skips uncommitted git repositories, preserves active toolchains, rejects symlinks, and enforces UID ownership

Ghost file detector that scans /proc/[pid]/fd for unlinked files held open by running processes

Surgical cleanup commands with dry-run mode, category explanation engine, and automated daily release checks

Engineering

Technical Specifications

Primary Languages: Go
Frameworks & Tooling: Go standard libraryLinux /proc
Architecture & Execution Model: Single static binary, pure standard library, concurrent worker scanners, fail-closed safety triage
Licensing Model: Dual: WaqfDPL-Mulzim 1.0 / AGPL-3.0 (waqf)
Release & Lineage: Active release cycle since 2026 · Maintained by @JadMadi

Knowledge

Frequently Asked Questions

Does StorageAudit delete files without confirmation?

No. Running storageaudit performs a read-only audit. Cleanup actions require explicit flags such as --clean-caches or --clean-all, and --dry-run lets you preview every deletion safely.

Will cleaning stale modules touch my active development work?

No. Repositories with uncommitted changes or unstaged edits are strictly protected and never modified. Only clean git trees inactive for at least 14 days are eligible.

Does StorageAudit collect telemetry or require network access?

No. StorageAudit is 100% local-first with zero telemetry. Its only network interaction is an optional daily check against GitHub releases for self-upgrades, which can be disabled with --no-update-check.