Point it at one folder
Choose your development folder. Every project below it is found from its marker files, including projects split in several modules.
Desktop app · 64-bit Windows
Kirekire scans your development folder and shows, project by project, the space taken by folders a build can recreate: node_modules, target, bin, obj… You choose what goes to the Recycle Bin.
No account No network Everything is recoverable
The idea
Every npm install, Maven build or Cargo run leaves gigabytes behind, and all of it can be rebuilt. Kirekire finds those projects for you, shows what you would win back, and leaves the decision to you.
Choose your development folder. Every project below it is found from its marker files, including projects split in several modules.
For each project: its total size, and the part that is only generated folders. Sort by space to free and the biggest wins come first.
Only the folders a build or an install can recreate are offered. They go to the Recycle Bin, and your sources are never touched.
How it works
The analysis reads. Deleting is a separate action you confirm.
Pick the folder where your projects live. The analysis only reads: it never writes, moves or deletes, and it does not follow shortcuts.
Each project shows its type, size, the space you can free, its dates, its README and whether it has Git. Sort by what you could win.
Tick projects, review the folders and the Git warnings, confirm. The generated folders move to the Recycle Bin.
The difference
Features
Projects
One table for your whole development folder: the space each project occupies and the space its generated folders take. Totals sit at the top, so you know at once how much is waiting. The analysis is saved, so the list is there when you reopen the app.
Real activity
The last update is the newest source file, so installs, builds and Git fetches do not make a dead project look alive. Select every project untouched for 6, 12 or 24 months in one step, and see how much space that frees before you decide.
Safe cleaning
Before anything moves, the dialog lists every folder and its size. Untick the ones you want to keep: Kirekire remembers, so dist starts unticked next time. Uncommitted changes, unpushed commits, a missing remote branch or no Git at all are shown up front.
Context
Click a project to read its README without leaving the app, rendered from the markdown on disk. The dialog lists the folders that could be deleted, opens the project folder in Explorer, and pins the project if you are still working on it.
And also
A pinned project is highlighted, its delete button is off, and its space is left out of what can be freed. It is never offered for deletion.
Kirekire counts everything it has moved to the Recycle Bin, across sessions. Empty the bin to get the space back.
Tick several projects and clean them one after the other through the same dialog, with the same checks on each.
Every row says whether the project is under Git, so a folder with no history stands out before you touch it.
A scan of a big folder takes minutes. The last result is kept and shown at startup; Refresh scans again and keeps the old list until the new one is complete.
The app follows the Windows light or dark mode. There is nothing to set up.
Screens
Real screenshots of the app, with made-up sample projects. Click to enlarge.
Supported projects
A folder is a project when it holds a build marker file, or a .git folder. The folders Kirekire offers to delete depend on the type, never on a guess.
package.json
node_modules, dist, .angular, .next, .nuxt, coverage…
pom.xml
target
build.gradle
build, .gradle, .kotlin
Cargo.toml
target
.csproj, .sln
bin, obj, .vs, TestResults
pyproject.toml
__pycache__, .venv, .pytest_cache, .mypy_cache…
go.mod
vendor
pubspec.yaml
.dart_tool, build
Also PHP, Ruby, C / C++ (CMake), Swift, Elixir, Scala, Clojure, Haskell, Unity, Unreal Engine, Xcode, Terraform, Zig and Godot.
Our principles
The analysis never writes, moves or deletes, and it does not follow symbolic links. Deleting is a separate, confirmed action.
No account, no telemetry, no network call. The README you read comes from your disk, and its links are removed.
The window that shows the list cannot ask for an arbitrary path to be deleted: the app only acts on projects its own scan found.
Folders go to the Recycle Bin, not into thin air. Restore them from there, or run your install command to rebuild them.
FAQ
No. It only offers folders that a build or an install can recreate, such as node_modules or target. Your sources are not touched, and pinned projects are never offered at all.
Yes, as long as the Recycle Bin has not been emptied: the folders are moved there, not deleted for good. The space is only returned to you when you empty the bin.
Because an npm install or a git fetch touches thousands of files without being work on the project. Kirekire dates a project from its newest source file, outside generated folders and .git.
A folder that holds a build marker file (package.json, pom.xml, Cargo.toml…) or a .git folder. A project split in modules is read module by module, so a root holding only .git over a package.json and a pom.xml is a JavaScript and Java project.
It runs a read-only git status and warns about uncommitted changes, unpushed commits, a missing remote branch, or no Git at all. The warnings inform you; the decision stays yours.
No. There is no account, no telemetry and no connection. The analysis and its results stay on your computer.
The sum of its file sizes, not disk blocks, so the size on disk can be a little larger. That is close enough to rank projects.
On 64-bit Windows for now.
In the Download section of this page, as soon as the first version is published.
See what your old projects are costing you, then decide. No account, no server, nothing sent anywhere.
Download for Windows