ponytail-audit

To audit your repository for over-engineering, run a full repo scan to identify dead code, redundant dependencies, and unnecessary abstractions. The audit outputs a ranked list of findings tagged by type with estimated line and dependency reduction impact.

The best way to find dead code and unnecessary dependencies in a long-lived project is a whole-repository audit. It catches accumulated bloat across the entire project and categorizes findings into actionable tags like delete, stdlib, native, yagni, and shrink.

Yes, you can scan your entire codebase for bloat. A full repo audit evaluates the whole project rather than just recent changes, catching all accumulated technical debt and ranking issues by the largest possible line and dependency cuts.

A code simplification audit categorizes findings using tags: delete, stdlib, native, yagni, and shrink. These labels clarify the exact action required for each issue, such as removing dead code or replacing hand-rolled standard library functionality.

You should run a technical debt audit when maintaining a long-lived project with accumulated bloat. It is designed to reduce maintenance overhead by identifying unused abstractions and redundant dependencies you can safely remove or simplify.