A tool that cleans dependency directories and build artifacts from projects across 20+ programming languages and frameworks.
Kondo is a disk cleanup tool that removes dependency directories and build artifacts from software projects to save storage space. It automatically detects project types across more than 20 languages and frameworks—such as Node.js, Rust, Python, and Java—and deletes folders like `node_modules`, `target`, and `build`. This helps developers free up gigabytes of space, especially useful for backups, trying out many projects, or keeping systems lean.
Developers who work with multiple programming languages, experiment with many projects, or need to reduce storage usage for backups and archival. It's also valuable for anyone managing large codebases with heavy dependency footprints.
Kondo stands out by supporting a wide range of project types in a single tool, offering both CLI and GUI interfaces, and including safety features like prompts. Unlike language-specific cleaners, it provides a unified solution for multi-language environments.
Cleans dependencies and build artifacts from your projects.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports over 20 project types including Rust, Node.js, Python, and Java, as listed in the README, making it a versatile solution for multi-language development environments.
Offers both CLI for automation and GUI for visual management, providing options for different user workflows, with installation via package managers like winget and Homebrew.
Allows targeting projects older than a specified period (e.g., with --older flag), enabling efficient cleanup of stale codebases without manual inspection.
Includes warnings and prompts before deletion, as emphasized in usage notes, reducing the risk of accidental data loss compared to raw rm -rf commands.
Once deletions are confirmed, there is no built-in recovery or trash mechanism, which increases the risk of permanent data loss despite the safety prompts.
On Linux, the GUI requires platform-specific dependencies, as noted in the build instructions, making setup more involved compared to the straightforward CLI installation.
Primarily targets common dependency folders; custom build outputs or unconventional project layouts may not be handled, requiring manual workarounds or additional tools.