dev-prune-linux-arm64 1.6.0 → 1.7.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +769 -0
- package/bin/dev-prune +0 -0
- package/package.json +2 -2
package/README.md
ADDED
|
@@ -0,0 +1,769 @@
|
|
|
1
|
+
# dev-prune-linux-arm64
|
|
2
|
+
|
|
3
|
+
**Do not install this package.** Install [`dev-prune`](https://www.npmjs.com/package/dev-prune):
|
|
4
|
+
|
|
5
|
+
```sh
|
|
6
|
+
npm install -g dev-prune
|
|
7
|
+
```
|
|
8
|
+
|
|
9
|
+
This package holds nothing but the prebuilt `dev-prune` binary for **linux arm64**.
|
|
10
|
+
It exists because npm has no other way to ship a per-platform executable: `dev-prune`
|
|
11
|
+
lists all seven platform packages as optional dependencies, and npm installs only the one
|
|
12
|
+
matching your machine. Installing this one directly gives you a binary with no launcher
|
|
13
|
+
and no upgrade path.
|
|
14
|
+
|
|
15
|
+
Documentation: <https://devprune.vkrishna04.me>
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
What follows is the dev-prune README, so this page describes the tool rather than just
|
|
20
|
+
refusing to be installed. Every command in it is run through the dispatcher package,
|
|
21
|
+
not through this one.
|
|
22
|
+
|
|
23
|
+
---
|
|
24
|
+
|
|
25
|
+
<div align="center">
|
|
26
|
+
|
|
27
|
+
<img src="assets/readme-banner.png" alt="dev-prune — get the gigabytes back, lose nothing" width="820" />
|
|
28
|
+
|
|
29
|
+
# `dev-prune`
|
|
30
|
+
|
|
31
|
+
### Get the gigabytes back. Lose nothing.
|
|
32
|
+
|
|
33
|
+
**Reclaim the disk space your idle repositories are sitting on — without ever deleting
|
|
34
|
+
something a lockfile cannot put back.**
|
|
35
|
+
|
|
36
|
+
[](https://crates.io/crates/dev-prune) [](https://pypi.org/project/dev-prune/) [](LICENSE.md) [](https://www.rust-lang.org/) [](docs/RELEASES_AND_MANUAL_INSTALL.md)
|
|
37
|
+
|
|
38
|
+
[](https://github.com/Life-Experimentalist/dev-prune/actions/workflows/ci.yml) [](https://devprune.vkrishna04.me/) [](https://www.npmjs.com/package/dev-prune)
|
|
39
|
+
|
|
40
|
+
[**Website**](https://devprune.vkrishna04.me/) · [**Documentation**](docs/README.md) · [**CLI reference**](docs/CLI_REFERENCE.md) · [**Safety invariants**](docs/SAFETY_INVARIANTS.md) · [**Changelog**](CHANGELOG.md)
|
|
41
|
+
|
|
42
|
+
`devp` is the same binary under a shorter name · Windows, macOS and Linux · Apache-2.0 · by [VKrishna04](https://vkrishna04.me)
|
|
43
|
+
|
|
44
|
+
</div>
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
`node_modules`, `.venv`, `target` and `vendor` are the largest directories on most
|
|
49
|
+
developers' machines, and the least valuable: every byte in them is described by a
|
|
50
|
+
lockfile that is already committed. A project you have not opened since March is holding
|
|
51
|
+
gigabytes hostage for a build you are not running.
|
|
52
|
+
|
|
53
|
+
`dev-prune` finds those directories across every Git repository you register, and deletes
|
|
54
|
+
them — but only after proving the exact command that puts them back would succeed. It is
|
|
55
|
+
a single Rust binary, installs its own background schedule, and answers to two names:
|
|
56
|
+
`dev-prune` and `devp`.
|
|
57
|
+
|
|
58
|
+
> [!IMPORTANT]
|
|
59
|
+
> **The rule the whole tool is built around:** nothing is deleted unless dev-prune has
|
|
60
|
+
> just verified, read-only, that its lockfile can rebuild it. There is no flag to skip
|
|
61
|
+
> that check. `--ignore-idle` lifts the idle-day wait and *nothing else*.
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## Contents
|
|
66
|
+
|
|
67
|
+
<div align="center">
|
|
68
|
+
|
|
69
|
+
**Start here** [Install](#install) · [Editors](#in-your-editor) · [60-second tour](#60-second-tour) · [What it looks like](#what-it-looks-like)
|
|
70
|
+
|
|
71
|
+
**How it thinks** [Why it is safe](#why-it-is-safe) · [Features](#features) · [Commands](#commands) · [Ecosystems](#supported-ecosystems) · [Monorepos](#repositories-with-more-than-one-ecosystem)
|
|
72
|
+
|
|
73
|
+
**Running it** [Configuration](#configuration) · [Automation](#background-automation) · [Comparison](#how-it-compares) · [Architecture](#architecture) · [Docs](#documentation)
|
|
74
|
+
|
|
75
|
+
</div>
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## Install
|
|
80
|
+
|
|
81
|
+
### One-liner
|
|
82
|
+
|
|
83
|
+
Pick the line for the shell you are actually typing into. Pasting the first one into a
|
|
84
|
+
Command Prompt is the most common install failure there is — it answers
|
|
85
|
+
`'sh' is not recognized as an internal or external command`, because `sh` is a Unix shell
|
|
86
|
+
and Windows does not ship one.
|
|
87
|
+
|
|
88
|
+
**Linux, macOS, or a Unix shell on Windows** — Git Bash, MSYS2, Cygwin, WSL:
|
|
89
|
+
|
|
90
|
+
```bash
|
|
91
|
+
curl -fsSL https://devprune.vkrishna04.me/install.sh | sh
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
**Windows PowerShell** — the blue or black `PS>` prompt, and Windows Terminal's default:
|
|
95
|
+
|
|
96
|
+
```powershell
|
|
97
|
+
iwr -useb https://devprune.vkrishna04.me/install.ps1 | iex
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
**Windows Command Prompt** — the `C:\>` prompt, which has no `iwr` of its own:
|
|
101
|
+
|
|
102
|
+
```bat
|
|
103
|
+
powershell -NoProfile -ExecutionPolicy Bypass -Command "iwr -useb https://devprune.vkrishna04.me/install.ps1 | iex"
|
|
104
|
+
```
|
|
105
|
+
|
|
106
|
+
All three download the prebuilt binary for your platform, verify its published SHA-256,
|
|
107
|
+
put it on `PATH`, and run `dev-prune setup`. Pass `--no-auto-setup` / `-NoAutoSetup` to
|
|
108
|
+
skip that last step.
|
|
109
|
+
|
|
110
|
+
The Command Prompt form installs identically to the PowerShell one, but `cmd` cannot
|
|
111
|
+
inherit the `PATH` the installer sets in its own process, so `devp` resolves in the *next*
|
|
112
|
+
Command Prompt you open rather than the current one. PowerShell does not have that
|
|
113
|
+
problem.
|
|
114
|
+
|
|
115
|
+
### From a package manager
|
|
116
|
+
|
|
117
|
+
```bash
|
|
118
|
+
uv tool install dev-prune # or: uvx dev-prune status
|
|
119
|
+
pipx install dev-prune
|
|
120
|
+
pip install dev-prune
|
|
121
|
+
cargo binstall dev-prune # fetches the prebuilt release archive
|
|
122
|
+
cargo install dev-prune # builds from source, needs Rust 1.88+
|
|
123
|
+
```
|
|
124
|
+
|
|
125
|
+
The PyPI packages **contain the binary** — there is no download step at install time,
|
|
126
|
+
so they work behind a registry mirror and offline. Everything but `cargo install` ships
|
|
127
|
+
a prebuilt executable.
|
|
128
|
+
|
|
129
|
+
crates.io stores source and nothing else, so `cargo install` has no binary to fetch and
|
|
130
|
+
always compiles. [`cargo binstall`](https://github.com/cargo-bins/cargo-binstall) is the
|
|
131
|
+
one that downloads: `Cargo.toml` tells it where this project's release archives live, so
|
|
132
|
+
it unpacks the same executable the installers use, with no toolchain involved.
|
|
133
|
+
|
|
134
|
+
Homebrew and Scoop each have a one-file tap and bucket, which exist so that upgrades keep
|
|
135
|
+
arriving:
|
|
136
|
+
|
|
137
|
+
```bash
|
|
138
|
+
brew tap Life-Experimentalist/tap
|
|
139
|
+
brew install dev-prune
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
```powershell
|
|
143
|
+
scoop bucket add life-experimentalist https://github.com/Life-Experimentalist/scoop-bucket
|
|
144
|
+
scoop install dev-prune
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
Both also install straight from a URL with nothing tapped or added, because the file
|
|
148
|
+
carries the SHA-256 of the archive it installs — but a formula that belongs to no tap is
|
|
149
|
+
one `brew upgrade` will never look at again:
|
|
150
|
+
|
|
151
|
+
```bash
|
|
152
|
+
brew install https://raw.githubusercontent.com/Life-Experimentalist/dev-prune/main/packaging/homebrew/dev-prune.rb
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
```powershell
|
|
156
|
+
scoop install https://raw.githubusercontent.com/Life-Experimentalist/dev-prune/main/packaging/scoop/dev-prune.json
|
|
157
|
+
```
|
|
158
|
+
|
|
159
|
+
WinGet is [submitted and in review](https://github.com/microsoft/winget-pkgs/pull/422665);
|
|
160
|
+
`winget install VKrishna04.dev-prune` starts resolving when that pull request merges.
|
|
161
|
+
|
|
162
|
+
The two Python entry points differ in where they land. `pip install` follows whichever
|
|
163
|
+
environment is active, so inside a virtualenv `devp` lives in that venv's `Scripts`/`bin`
|
|
164
|
+
and disappears with it; `pip install --user`, `pipx` and `uv tool install` are the
|
|
165
|
+
machine-wide forms. [Where each one puts the executables](docs/troubleshooting/INSTALLATION_ISSUES.md#6-uv-tool-install-put-the-executables-somewhere-unexpected).
|
|
166
|
+
|
|
167
|
+
### Direct download
|
|
168
|
+
|
|
169
|
+
Seven checksummed archives per release on
|
|
170
|
+
[GitHub Releases](https://github.com/Life-Experimentalist/dev-prune/releases) — Windows,
|
|
171
|
+
macOS and Linux on x64 and arm64, plus a 32-bit `windows-x86` build for machines with no
|
|
172
|
+
64-bit mode. The Linux binaries are statically linked against musl, so one file per
|
|
173
|
+
architecture runs on every distribution including Alpine.
|
|
174
|
+
|
|
175
|
+
Manual install and build-from-source:
|
|
176
|
+
[docs/RELEASES_AND_MANUAL_INSTALL.md](docs/RELEASES_AND_MANUAL_INSTALL.md).
|
|
177
|
+
|
|
178
|
+
### In your editor
|
|
179
|
+
|
|
180
|
+
There is a companion extension. It validates `.devprune.json` as you type — every key,
|
|
181
|
+
every adapter name, every enum, from the schema bundled inside it rather than fetched — and
|
|
182
|
+
puts the workspace's reclaimable size in the status bar, so you can see what a repository
|
|
183
|
+
is holding without leaving the window.
|
|
184
|
+
|
|
185
|
+
[](https://marketplace.visualstudio.com/items?itemName=VKrishna04.dev-prune) [](https://open-vsx.org/extension/VKrishna04/dev-prune)
|
|
186
|
+
|
|
187
|
+
```bash
|
|
188
|
+
code --install-extension VKrishna04.dev-prune
|
|
189
|
+
```
|
|
190
|
+
|
|
191
|
+
Open VSX is the same extension for the editors that cannot reach Microsoft's marketplace —
|
|
192
|
+
VSCodium, Cursor, Windsurf, Positron, Kiro. You do not have to pick: `devp setup` offers
|
|
193
|
+
to install it once, at a terminal, into whichever of those it finds, each from its own
|
|
194
|
+
registry.
|
|
195
|
+
|
|
196
|
+
**JetBrains IDEs need no extension at all.** The config schema is registered with
|
|
197
|
+
[SchemaStore](https://www.schemastore.org/), so IntelliJ, PyCharm, WebStorm, GoLand,
|
|
198
|
+
RubyMine and Rider validate `.devprune.json` out of the box — as do Visual Studio, Neovim
|
|
199
|
+
and Zed.
|
|
200
|
+
|
|
201
|
+
**And your coding agent gets the same treatment.** `devp skill --agent <editor>` writes the
|
|
202
|
+
rules file that editor actually reads — `.github/copilot-instructions.md`, `.cursor/rules/`,
|
|
203
|
+
`CLAUDE.md`, `.junie/guidelines.md` and the rest — so an agent working in the repository
|
|
204
|
+
knows what dev-prune will and will not delete before it suggests anything.
|
|
205
|
+
|
|
206
|
+
Everything about editors, in one place:
|
|
207
|
+
[docs/IDE_INTEGRATION.md](docs/IDE_INTEGRATION.md).
|
|
208
|
+
|
|
209
|
+
### Let an AI assistant do it
|
|
210
|
+
|
|
211
|
+
Copy the prompt below and paste it to Claude Code, Cursor, GitHub Copilot, Windsurf, or
|
|
212
|
+
any terminal-capable agent — it installs, verifies, and registers your projects for you.
|
|
213
|
+
[More detail and per-tool notes.](docs/AI_SETUP_PROMPT.md)
|
|
214
|
+
|
|
215
|
+
````text
|
|
216
|
+
Install and set up `dev-prune` (binary name `devp`), a lockfile-safe workspace cleaner,
|
|
217
|
+
on this machine. Follow these steps exactly and do not improvise beyond them.
|
|
218
|
+
|
|
219
|
+
1. Detect the OS and run the matching official installer, nothing else:
|
|
220
|
+
- macOS or Linux:
|
|
221
|
+
curl -fsSL https://devprune.vkrishna04.me/install.sh | sh
|
|
222
|
+
- Windows (PowerShell):
|
|
223
|
+
iwr -useb https://devprune.vkrishna04.me/install.ps1 | iex
|
|
224
|
+
- If a Rust toolchain is already present and you cannot reach the network, you may
|
|
225
|
+
instead run: cargo install dev-prune
|
|
226
|
+
Do NOT download binaries from anywhere other than devprune.vkrishna04.me or the
|
|
227
|
+
project's GitHub releases, and do NOT edit PATH, the registry, or any OS scheduler by
|
|
228
|
+
hand — the installer and `devp setup` do all of that themselves.
|
|
229
|
+
|
|
230
|
+
2. Open a NEW terminal (so the updated PATH is in effect) and verify:
|
|
231
|
+
devp --version
|
|
232
|
+
devp doctor
|
|
233
|
+
`devp doctor` must exit 0. If it prints warnings, read them out to me; do not try to
|
|
234
|
+
"fix" the scheduler or hooks yourself — they are self-installing.
|
|
235
|
+
|
|
236
|
+
3. Ask me which project directories to keep clean, then register each one:
|
|
237
|
+
devp init <path>
|
|
238
|
+
Do not register directories I did not name. `devp init` only records a directory; it
|
|
239
|
+
never deletes anything on its own.
|
|
240
|
+
|
|
241
|
+
4. Show me the result and stop:
|
|
242
|
+
devp status
|
|
243
|
+
|
|
244
|
+
Notes you should rely on, not work around:
|
|
245
|
+
- Installation already registered a background pass (every 2 days) and, on Windows, a
|
|
246
|
+
windowless task that never flashes a console window. You do not need to configure any
|
|
247
|
+
of this.
|
|
248
|
+
- Nothing is ever deleted unless a lockfile can rebuild it, the repo has been idle past
|
|
249
|
+
the threshold, and (interactively) I confirm. Run `devp run --dry-run` if I want a
|
|
250
|
+
preview.
|
|
251
|
+
- To undo the whole thing later: `devp uninstall`.
|
|
252
|
+
````
|
|
253
|
+
|
|
254
|
+
Every install channel in detail: [docs/DISTRIBUTION.md](docs/DISTRIBUTION.md).
|
|
255
|
+
|
|
256
|
+
> [!TIP]
|
|
257
|
+
> **`devp` is a real executable, not a shell alias.** Installation puts a second binary
|
|
258
|
+
> next to `dev-prune`, so the short name works in cmd, PowerShell, bash, fish, an IDE
|
|
259
|
+
> terminal and a scheduled task alike — with no profile to re-source, and no chance of an
|
|
260
|
+
> upgrade leaving `devp` on the old version.
|
|
261
|
+
|
|
262
|
+
---
|
|
263
|
+
|
|
264
|
+
## 60-second tour
|
|
265
|
+
|
|
266
|
+
```bash
|
|
267
|
+
devp init ~/Projects # register every Git repository under a tree
|
|
268
|
+
devp status # dashboard: what is tracked, what is reclaimable
|
|
269
|
+
devp run --dry-run # what a pass would delete — changes nothing
|
|
270
|
+
devp run # do it, after confirming
|
|
271
|
+
devp restore --last-run # put back exactly what that pass deleted
|
|
272
|
+
```
|
|
273
|
+
|
|
274
|
+
A few more worth knowing on day one:
|
|
275
|
+
|
|
276
|
+
```bash
|
|
277
|
+
devp stats # how much has been reclaimed so far, and by which repositories
|
|
278
|
+
devp caches # every package manager cache, sized. The report deletes nothing
|
|
279
|
+
devp status --drift # anything installed that the lockfiles don't record?
|
|
280
|
+
devp doctor . # why is this repository not being pruned?
|
|
281
|
+
devp doctor --fix # repair a broken integration — never a first-time install
|
|
282
|
+
devp -V # version, OS, architecture, config path, PATH audit
|
|
283
|
+
```
|
|
284
|
+
|
|
285
|
+
---
|
|
286
|
+
|
|
287
|
+
## What it looks like
|
|
288
|
+
|
|
289
|
+
<details open>
|
|
290
|
+
<summary><b><code>devp run --dry-run</code></b> — the plan, before anything is touched</summary>
|
|
291
|
+
|
|
292
|
+
```console
|
|
293
|
+
$ devp run --dry-run
|
|
294
|
+
|
|
295
|
+
dev-prune run (DRY RUN)
|
|
296
|
+
→ Scanning 4 registered repositories for prune candidates...
|
|
297
|
+
|
|
298
|
+
Prune Candidates & Space Savings Calculation
|
|
299
|
+
→ • ~/Code/acme-api → node_modules (412.7 MiB) [pnpm]
|
|
300
|
+
→ • ~/Code/acme-api → services/worker/.venv (188.2 MiB) [uv]
|
|
301
|
+
→ • ~/Code/render-farm → target (2.14 GiB) [cargo]
|
|
302
|
+
→ • ~/Code/edge-proxy → vendor (96.4 MiB) [go]
|
|
303
|
+
|
|
304
|
+
Summary (Dry Run)
|
|
305
|
+
→ Would free 2.82 GiB across 4 bloat directories.
|
|
306
|
+
```
|
|
307
|
+
|
|
308
|
+
</details>
|
|
309
|
+
|
|
310
|
+
<details>
|
|
311
|
+
<summary><b><code>devp status</code></b> — the dashboard, or a plain table with no TTY</summary>
|
|
312
|
+
|
|
313
|
+
```console
|
|
314
|
+
$ devp status
|
|
315
|
+
|
|
316
|
+
→ Global Config Location: ~/.config/dev-prune/registry.json
|
|
317
|
+
→ Background OS Daemon: Installed
|
|
318
|
+
→ Background Git Hooks: Installed
|
|
319
|
+
→ Global Command Timeout: 600s (10m)
|
|
320
|
+
→ Tracked Repositories: 4
|
|
321
|
+
→ Historical Space Saved: 6.31 GiB across 9 prune passes
|
|
322
|
+
|
|
323
|
+
dev-prune status
|
|
324
|
+
|
|
325
|
+
# Repository Status / Reason Adapters Bloat Last Activity Last Pruned
|
|
326
|
+
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
|
|
327
|
+
1 acme-api Candidate pnpm+uv 600.9 MiB 2026-04-02 Never
|
|
328
|
+
2 render-farm Candidate cargo 2.14 GiB 2026-03-11 2026-01-08
|
|
329
|
+
3 edge-proxy Candidate go 96.4 MiB 2026-05-19 Never
|
|
330
|
+
4 dashboard Active (not idle) npm 314.0 MiB 2026-08-12 2026-06-30
|
|
331
|
+
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
|
|
332
|
+
→ Total: 4 repos | 3 candidates | 3.13 GiB reclaimable
|
|
333
|
+
```
|
|
334
|
+
|
|
335
|
+
Keys: `↑`/`↓` move, `p` pre-selects every candidate, `Space` deselects the one you are
|
|
336
|
+
keeping, `Enter` prunes the rest, `i` toggles ignore for a repository, `q` exits.
|
|
337
|
+
|
|
338
|
+
</details>
|
|
339
|
+
|
|
340
|
+
<details>
|
|
341
|
+
<summary><b><code>devp caches</code></b> — where the rest of the disk went</summary>
|
|
342
|
+
|
|
343
|
+
```console
|
|
344
|
+
$ devp caches
|
|
345
|
+
|
|
346
|
+
Package manager caches
|
|
347
|
+
|
|
348
|
+
uv cache 16.25 GiB ~/.cache/uv
|
|
349
|
+
clear: uv cache prune
|
|
350
|
+
|
|
351
|
+
npm cache 8.97 GiB ~/.npm
|
|
352
|
+
clear: npm cache clean --force
|
|
353
|
+
|
|
354
|
+
go build cache 371.75 MiB ~/.cache/go-build
|
|
355
|
+
clear: go clean -cache
|
|
356
|
+
compiled build artifacts; clearing them means the next build is a cold one
|
|
357
|
+
|
|
358
|
+
cargo registry sources 104.75 MiB ~/.cargo/registry/src
|
|
359
|
+
clear: rm -rf ~/.cargo/registry/src
|
|
360
|
+
unpacked copies of the archives above; cargo re-extracts these offline
|
|
361
|
+
|
|
362
|
+
… (pip, bun, pnpm, go module cache, cargo registry cache)
|
|
363
|
+
|
|
364
|
+
Total 27.26 GiB across 9 caches
|
|
365
|
+
|
|
366
|
+
→ Nothing above was deleted, and dev-prune never deletes any of it.
|
|
367
|
+
```
|
|
368
|
+
|
|
369
|
+
A cache lives outside every repository and is shared by all of them, so no single
|
|
370
|
+
lockfile can prove it recoverable — and it is what makes `devp restore` fast. `devp
|
|
371
|
+
caches` reports and prints the clear command; running it is your decision.
|
|
372
|
+
|
|
373
|
+
</details>
|
|
374
|
+
|
|
375
|
+
<details>
|
|
376
|
+
<summary><b><code>devp doctor .</code></b> — the one reason a repository is being skipped</summary>
|
|
377
|
+
|
|
378
|
+
```console
|
|
379
|
+
$ devp doctor .
|
|
380
|
+
|
|
381
|
+
dev-prune doctor (~/Code/dashboard)
|
|
382
|
+
|
|
383
|
+
Repository
|
|
384
|
+
Git repository ✓ yes
|
|
385
|
+
Registered ✓ yes, since 2026-04-11
|
|
386
|
+
.devprune.json parses; idle_days 20
|
|
387
|
+
Opt-out none
|
|
388
|
+
Activity 2026-08-12 (0 days ago), threshold 20 — active
|
|
389
|
+
Size floor none — every recognised directory counts
|
|
390
|
+
Scan depth 6 levels below the root
|
|
391
|
+
|
|
392
|
+
Projects
|
|
393
|
+
|
|
394
|
+
. (npm)
|
|
395
|
+
Lockfile ✓ package-lock.json present
|
|
396
|
+
Bloat ✓ node_modules (314.0 MiB)
|
|
397
|
+
|
|
398
|
+
Verdict
|
|
399
|
+
✗ Would `devp run` prune this? No — active within the last 20 days.
|
|
400
|
+
`devp --ignore-idle run ~/Code/dashboard` overrides exactly that check and nothing else.
|
|
401
|
+
```
|
|
402
|
+
|
|
403
|
+
It runs no package manager and repairs nothing, so it is safe to run twice — once to see
|
|
404
|
+
the problem, once to confirm the fix. Without a path it audits the installation instead:
|
|
405
|
+
binary location and `PATH`, the registry and every setting in it, the integrations, which
|
|
406
|
+
package managers are reachable, and the release-check state.
|
|
407
|
+
|
|
408
|
+
|
|
409
|
+
|
|
410
|
+
</details>
|
|
411
|
+
|
|
412
|
+
---
|
|
413
|
+
|
|
414
|
+
## Why it is safe
|
|
415
|
+
|
|
416
|
+
Seven invariants, enforced in code rather than by convention, none of which has a bypass
|
|
417
|
+
flag. Full detail and the reasoning behind each in
|
|
418
|
+
[docs/SAFETY_INVARIANTS.md](docs/SAFETY_INVARIANTS.md).
|
|
419
|
+
|
|
420
|
+
| # | Invariant | What it prevents |
|
|
421
|
+
| :---: | :-------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------ |
|
|
422
|
+
| 1 | **`.git` boundary** — only ever operates inside a directory holding a `.git` root | Deleting a `node_modules` that belongs to no repository and has no lockfile behind it |
|
|
423
|
+
| 2 | **Lockfile pre-verification** — the ecosystem's own read-only check must pass first | Deleting a tree whose lockfile has drifted, leaving a reinstall that fails |
|
|
424
|
+
| 3 | **Hybrid activity solver** — the later of the last commit and the newest source `mtime` | Pruning a project with a week of uncommitted work in it |
|
|
425
|
+
| 4 | **Atomic state writes** — write to a temp file, then rename | A registry corrupted by a crash or a power cut mid-write |
|
|
426
|
+
| 5 | **0ms ignore fast path** — `ignore.devprune.json` short-circuits before any parsing | A repository you opted out of being scanned at all |
|
|
427
|
+
| 6 | **Symlink and junction refusal** | Following a link out of the repository and deleting storage it does not own |
|
|
428
|
+
| 7 | **Nested repository boundary** | A submodule being deleted as part of its parent instead of on its own terms |
|
|
429
|
+
|
|
430
|
+
Verification is **read-only by default**: `npm ci --dry-run`, `uv lock --locked`, `cargo
|
|
431
|
+
metadata --locked`, `go mod download`. Each resolves the dependency graph against the
|
|
432
|
+
lockfile on disk and *fails* when the two disagree, instead of quietly rewriting the
|
|
433
|
+
lockfile and continuing. The writing form runs in exactly two cases — when no lockfile
|
|
434
|
+
exists at all, and when you have asked with `devp config set allow_manifest_rewrite true`
|
|
435
|
+
— because a pass can be started by the OS scheduler while you are away, and a background
|
|
436
|
+
process that leaves a dirty working tree is a surprise.
|
|
437
|
+
|
|
438
|
+
---
|
|
439
|
+
|
|
440
|
+
## Features
|
|
441
|
+
|
|
442
|
+
| What you get | What it means in practice |
|
|
443
|
+
| :-------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
444
|
+
| 🔒 **Lockfile-gated deletion** | Nothing goes without a passing read-only verification against `package-lock.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lock`, `uv.lock`, `requirements.txt`, `Cargo.lock` or `go.sum` |
|
|
445
|
+
| 🧩 **Any number of ecosystems per repository** | uv, npm and cargo in one root, or spread across `frontend/`, `services/api/` and `tools/cli/` — each discovered, verified and pruned on its own terms |
|
|
446
|
+
| ↩️ **One-command restore** | `devp restore .` reinstalls a tree; `devp restore --last-run` puts back exactly what the most recent pass deleted, across every repository it touched |
|
|
447
|
+
| 🕒 **Activity-aware** | Combines `git log` timestamps with source-file `mtime`, so uncommitted work protects a repository just as a commit does |
|
|
448
|
+
| 📊 **Cache report** | `devp caches` sizes every package manager cache and store on the machine — npm to cargo to Maven, Gradle, NuGet, vcpkg, Conan, Composer, CocoaPods and Hex — and prints the command that clears each. The report is read-only; `devp caches clear <manager>` runs that command for you, after asking. Nothing on a schedule ever touches a cache |
|
|
449
|
+
| 🩺 **`devp doctor`** | One read-only pass that ends by naming the *single* reason a repository would or would not be pruned. Runs no package manager, repairs nothing, safe to run twice. `devp doctor --fix` then mends what it found — installed-but-broken only |
|
|
450
|
+
| 🤖 **Self-installing automation** | OS-native scheduler (Task Scheduler, LaunchAgent, systemd user timer) and non-blocking Git hooks, installed at install time and restored after an upgrade. `auto_setup`, `auto_hooks`, `auto_daemon` or `DEV_PRUNE_NO_AUTO_SETUP=1` turn it off |
|
|
451
|
+
| ⚡ **0ms opt-out** | An `ignore.devprune.json` in a repository root is honoured by file presence alone — no read, no parse |
|
|
452
|
+
| 🔌 **`--json` on every reporting command** | `run`, `status`, `stats`, `trust` and `caches` each emit one versioned document on stdout, diagnostics on stderr. Built for scripts and agents |
|
|
453
|
+
| 🧠 **AI agent skill** | A token-lean `SKILL.md` embedded in the binary; `devp skill` exports it and prints onboarding prompts for Claude Code, Gemini Antigravity, Cursor, Windsurf, Copilot and OpenClaw |
|
|
454
|
+
| 🧰 **Editor extension** | Validates `.devprune.json` as you type and shows the workspace's reclaimable size in the status bar. `devp setup` offers to install it — once, only at a terminal — into VS Code, VSCodium, Cursor, Windsurf, Positron or Kiro, each from its own registry with the release `.vsix` as fallback. [docs/IDE_INTEGRATION.md](docs/IDE_INTEGRATION.md) |
|
|
455
|
+
| 🖼️ **File manager icons** | `devp icon` registers `*.devprune.json` with the OS file manager — a real `shared-mime-info` type plus hicolor icons on Linux, a folder icon on Windows. It never edits your editor settings, `PATH` or shell startup files |
|
|
456
|
+
| 🌏 **Unicode-safe paths** | A repository at `ワークスペース/项目目录名称测试/프론트엔드` scans, verifies, prunes and restores exactly like an ASCII one, on all three platforms. Terminal tables are padded by display *column*, not by character, so full-width CJK names keep `devp status` and `devp doctor` aligned. Accented Latin, Cyrillic, Arabic and emoji directory names too |
|
|
457
|
+
| 🚫 **No telemetry** | One optional unauthenticated `GET` to GitHub's public releases endpoint, at most weekly, no body and no identifier. Nothing else leaves the machine |
|
|
458
|
+
|
|
459
|
+
---
|
|
460
|
+
|
|
461
|
+
## Commands
|
|
462
|
+
|
|
463
|
+
| Command | Also | What it does |
|
|
464
|
+
| :--------------------- | :------------------------------------------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
465
|
+
| `devp init [PATHS]` | `scan`, `onboard` | Crawls directory trees for Git repositories and registers them, then runs the `setup` integration pass |
|
|
466
|
+
| `devp link [PATH]` | | Registers one repository |
|
|
467
|
+
| `devp unlink [PATH]` | `--missing` | Unregisters one; `--missing` drops every entry whose directory is gone, in one pass |
|
|
468
|
+
| `devp undo` | | Reverts the most recent `init` or `link` |
|
|
469
|
+
| `devp run [PATH]` | `--dry-run`, `--only`, `--skip`, `--except`, `--min-size`, `--json` | Prunes every registered repository, or one target |
|
|
470
|
+
| `devp status` | `--top N`, `--drift`, `--json` | Interactive dashboard; a plain table when there is no TTY. `--top N` shows only the N biggest repositories; `--drift` lists every environment holding packages its lockfile never recorded |
|
|
471
|
+
| `devp stats` | `--json` | What has already been reclaimed: lifetime total, prune passes, the last pass, and the biggest contributors |
|
|
472
|
+
| `devp completions` | `bash`, `zsh`, `fish`, `powershell`, `elvish` | Prints a shell completion script to stdout, generated from the same argument definitions the binary parses with |
|
|
473
|
+
| `devp caches` | `clear <manager\|all>`, `--json` | Sizes every package manager cache on the machine and prints the command that clears each. The report deletes nothing and nothing on a schedule ever will; `clear` empties one when you type it, after asking |
|
|
474
|
+
| `devp trust` | `--json` | What dev-prune may do on this machine: the guarantees the code enforces, then the scheduler, hooks and settings read live. Read-only |
|
|
475
|
+
| `devp restore [PATH]` | `--last-run` | Reinstalls dependencies for every project in a tree; `--last-run` undoes the last prune pass |
|
|
476
|
+
| `devp doctor [PATH]` | `--fix` | Diagnoses the installation, or one repository — ending with the single reason a pass would or would not touch it. `--fix` repairs what the checks found; it never performs a first-time install |
|
|
477
|
+
| `devp config [ACTION]` | `get`, `set`, `show`, `wizard`, `project`, `daemon`, `hook`, `icon` | Global settings, per-repository `.devprune.json`, scheduler, Git hooks, file manager icons |
|
|
478
|
+
| `devp setup` | `--status` | Installs any missing integration; `--status` only reports |
|
|
479
|
+
| `devp update` | `--offline`, `--install` | Prints the installed version, checks GitHub for a newer release, shows the upgrade command for your install channel; `--install` runs that upgrade through the channel that owns this copy |
|
|
480
|
+
| `devp skill` | `--agent <editor>` | Exports `SKILL.md` and prints AI agent onboarding prompts; `--agent` writes per-repository rules for 15 editors — Cursor, Windsurf, Antigravity, Cline, Roo, Kilo Code, Continue, Amazon Q, Kiro, Trae, Junie, Gemini CLI, Zed, Copilot or `AGENTS.md` |
|
|
481
|
+
| `devp man` | `--dir <dir>` | The manual as man pages, generated from the same argument definitions `--help` prints; alone it emits `devp(1)` to stdout, `--dir` writes the full set |
|
|
482
|
+
| `devp uninstall` | `--deep` | Removes the scheduler, hooks, both binaries and every other installed copy it can find on the machine; `--deep` also clears configuration |
|
|
483
|
+
| `devp -V` | | Version plus an environment audit: OS, architecture, config path, PATH activation |
|
|
484
|
+
|
|
485
|
+
`devp hook`, `devp daemon` and `devp icon` are shorthands for the `config` subcommands of
|
|
486
|
+
the same name, and `install` / `uninstall` / `on` / `off` work wherever `enable` /
|
|
487
|
+
`disable` do — so `devp hook install` and `devp config hook enable` are the same command.
|
|
488
|
+
A misspelled action is rejected rather than quietly reported as status.
|
|
489
|
+
|
|
490
|
+
`--help` is the manual: every command and every `config` subcommand carries long-form
|
|
491
|
+
help with worked examples — `devp run --help`, `devp config hook --help`, and so on at
|
|
492
|
+
every level — while `-h` keeps the short version.
|
|
493
|
+
|
|
494
|
+
Exit codes are a contract: `0` success, `1` failure, `2` unusable arguments. Full flag
|
|
495
|
+
list, every setting and the `--json` schema: **[docs/CLI_REFERENCE.md](docs/CLI_REFERENCE.md)**.
|
|
496
|
+
|
|
497
|
+
---
|
|
498
|
+
|
|
499
|
+
## Supported ecosystems
|
|
500
|
+
|
|
501
|
+
Adapters detect the project, verify the lockfile, and own the bloat directories:
|
|
502
|
+
|
|
503
|
+
| Ecosystem | Detected by | Bloat | Verification (read-only) | Restore |
|
|
504
|
+
| :---------------------------- | :------------------------------------------------------------ | :----------------------------------------- | :---------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------- |
|
|
505
|
+
| **npm** | `package-lock.json` | `node_modules` | `npm ci --dry-run --ignore-scripts` | `npm ci` |
|
|
506
|
+
| **pnpm** | `pnpm-lock.yaml` | `node_modules` | `pnpm install --lockfile-only --frozen-lockfile` | `pnpm install --frozen-lockfile` |
|
|
507
|
+
| **Yarn** | `yarn.lock` | `node_modules` | `yarn install --immutable --mode update-lockfile` (Berry); on Classic an existing `yarn.lock` is itself the proof | `yarn install --immutable` |
|
|
508
|
+
| **Bun** | `bun.lockb`, `bun.lock` | `node_modules` | `bun install --frozen-lockfile --dry-run --ignore-scripts` | `bun install --frozen-lockfile` |
|
|
509
|
+
| **uv** (Python) | `uv.lock`, `[tool.uv]` in `pyproject.toml` | `.venv` | `uv lock --locked` | `uv sync` |
|
|
510
|
+
| **Poetry** (Python) | `poetry.lock`, `[tool.poetry]` in `pyproject.toml` | `.venv` | `poetry check --lock`, plus no installed package the lockfile never recorded | `poetry install` |
|
|
511
|
+
| **PDM** (Python) | `pdm.lock`, `[tool.pdm]` or `pdm.backend` in `pyproject.toml` | `.venv`, `__pypackages__` | `pdm lock --check` | `pdm install` |
|
|
512
|
+
| **Pipenv** (Python) | `Pipfile` | `.venv` *(in-project installs only)* | `pipenv verify` | `pipenv install --deploy` |
|
|
513
|
+
| **venv** (Python) | `requirements.txt` + a directory containing `pyvenv.cfg` | every directory containing `pyvenv.cfg` | `requirements.txt` must exist and list at least one package | `python -m venv .venv && pip install -r requirements.txt` |
|
|
514
|
+
| **Cargo** (Rust) *(opt-in)* | `Cargo.toml` | `target` | `cargo metadata --locked` | *(rebuilt by the next `cargo build`)* |
|
|
515
|
+
| **Go** | `go.mod` | `vendor` | `go mod download` | `go mod vendor` |
|
|
516
|
+
| **Composer** (PHP) | `composer.json` | `vendor` | `composer validate --no-check-publish --no-check-all` | `composer install` |
|
|
517
|
+
| **Bundler** (Ruby) | `Gemfile` | `vendor/bundle` *(vendored installs only)* | `bundle lock --check` | `bundle install` |
|
|
518
|
+
| **CocoaPods** (Apple) | `Podfile` | `Pods` | `Podfile.lock` carries its `SPEC CHECKSUMS` section and is no older than the `Podfile` | `pod install` |
|
|
519
|
+
| **Mix** (Elixir) | `mix.exs` | `deps` | `mix.lock` is a complete Elixir map and no older than `mix.exs` | `mix deps.get` |
|
|
520
|
+
| **Terraform** | any `*.tf` / `*.tf.json` | `.terraform/providers` | `.terraform.lock.hcl` records at least one provider | `terraform init -backend=false` |
|
|
521
|
+
| **Gradle** *(opt-in)* | `build.gradle[.kts]`, `settings.gradle[.kts]` | `build`, `.gradle` | manifest present and readable — the rebuild-from-source proof | *(rebuilt by the next `./gradlew build`)* |
|
|
522
|
+
| **Maven** *(opt-in)* | `pom.xml` | `target` | `pom.xml` parses as a Maven manifest | *(rebuilt by the next `mvn package`)* |
|
|
523
|
+
| **SwiftPM** *(opt-in)* | `Package.swift` | `.build` | `Package.swift` declares a `Package(` — the rebuild-from-source proof | *(rebuilt by the next `swift build`)* |
|
|
524
|
+
| **Dart / Flutter** *(opt-in)* | `pubspec.yaml` | `.dart_tool` | `pubspec.lock` has a `packages:` section and is no older than `pubspec.yaml` | `dart pub get` / `flutter pub get` |
|
|
525
|
+
| **Mix `_build/`** *(opt-in)* | `mix.exs` | `_build` | `mix.exs` and `mix.lock` both present — the rebuild-from-source proof | *(rebuilt by the next `mix compile`)* |
|
|
526
|
+
|
|
527
|
+
A required binary that is missing is a reason to skip, never a reason to delete: if `npm`
|
|
528
|
+
is not on `PATH`, the `node_modules` it owns is left exactly where it is.
|
|
529
|
+
|
|
530
|
+
The six build-tool adapters ship **disabled**, because a build tree is regenerated
|
|
531
|
+
by recompiling, not downloading — it costs more to get back. `devp config set
|
|
532
|
+
enable_cargo true` / `enable_gradle true` / `enable_maven true` / `enable_swift true` /
|
|
533
|
+
`enable_dart true` / `enable_mix_build true` switches them on, and their candidates wait for `build_idle_days` (45 by default),
|
|
534
|
+
applied as the *maximum* of it and `idle_days` — the build-tool gate only ever makes
|
|
535
|
+
pruning later, never earlier.
|
|
536
|
+
|
|
537
|
+
Any one adapter can be made to wait longer than the rest: `devp config set
|
|
538
|
+
adapter_idle_days cargo=90,npm=30` sets a per-adapter floor, applied as
|
|
539
|
+
`max(idle_days, build_idle_days, adapter_idle_days[name])`. `devp config wizard` edits
|
|
540
|
+
it beside the adapter checklist, grouped by language, where one heading sets the same
|
|
541
|
+
window for every adapter under it.
|
|
542
|
+
|
|
543
|
+
Bundler and Pipenv claim only the install that lives *inside* the repository: the
|
|
544
|
+
`vendor/bundle` a project gets from `bundle config set path vendor/bundle`, and the
|
|
545
|
+
`.venv` that appears when `PIPENV_VENV_IN_PROJECT` is set. Both tools default to a
|
|
546
|
+
shared store under your home directory instead, and dev-prune does not go near those at
|
|
547
|
+
all: a shared gem home or virtualenv directory is where other projects' dependencies are
|
|
548
|
+
*installed*, not a cache, and no single lockfile could prove its contents recoverable.
|
|
549
|
+
For the same reason Composer leaves `vendor/` alone entirely when a `vendor/bundle` is
|
|
550
|
+
sitting inside it: no `composer install` puts those gems back.
|
|
551
|
+
|
|
552
|
+
Any adapter can be switched off outright with `devp config set disabled_adapters
|
|
553
|
+
<names>` — a disabled adapter is not detected, not counted by `stats`, not probed
|
|
554
|
+
for by `doctor` and never pruned, exactly as if that ecosystem were not installed.
|
|
555
|
+
|
|
556
|
+
> [!TIP]
|
|
557
|
+
> Adding an ecosystem is documented end to end in
|
|
558
|
+
> [docs/ADDING_ADAPTERS.md](docs/ADDING_ADAPTERS.md) — trait, registration, tests.
|
|
559
|
+
|
|
560
|
+
### Repositories with more than one ecosystem
|
|
561
|
+
|
|
562
|
+
A repository is not assumed to be one project. dev-prune walks the root and up to
|
|
563
|
+
`scan_depth` levels below it — six by default, `devp config set scan_depth N` to change
|
|
564
|
+
it, or `"scan_depth"` in a repository's `.devprune.json` for just that tree. Every
|
|
565
|
+
directory a package manager recognises is verified and pruned on its own terms. All three
|
|
566
|
+
of these work:
|
|
567
|
+
|
|
568
|
+
```
|
|
569
|
+
monorepo/ monorepo/ monorepo/
|
|
570
|
+
├── package-lock.json ├── frontend/ ├── Cargo.toml
|
|
571
|
+
├── uv.lock │ └── pnpm-lock.yaml ├── web/
|
|
572
|
+
└── Cargo.toml ├── services/api/ │ └── package-lock.json
|
|
573
|
+
│ └── uv.lock └── scripts/
|
|
574
|
+
three managers, one root └── tools/cli/ └── requirements.txt
|
|
575
|
+
└── Cargo.toml
|
|
576
|
+
root + nested, mixed
|
|
577
|
+
one manager per subtree
|
|
578
|
+
```
|
|
579
|
+
|
|
580
|
+
Results are reported by repository-relative path, so a monorepo reads unambiguously:
|
|
581
|
+
|
|
582
|
+
```
|
|
583
|
+
• MyMonorepo → frontend/node_modules (412.7 MiB) [pnpm]
|
|
584
|
+
• MyMonorepo → services/api/.venv (188.2 MiB) [uv]
|
|
585
|
+
• MyMonorepo → tools/cli/target (1.4 GiB) [cargo]
|
|
586
|
+
```
|
|
587
|
+
|
|
588
|
+
The walk never descends into `node_modules`, `target`, `vendor`, virtual environments,
|
|
589
|
+
hidden directories, or nested repositories — a submodule is pruned as itself, never as
|
|
590
|
+
part of its parent.
|
|
591
|
+
|
|
592
|
+
When npm, pnpm, yarn and bun all claim the same `node_modules`, exactly one is chosen,
|
|
593
|
+
strongest signal first:
|
|
594
|
+
|
|
595
|
+
1. the `packageManager` field in `package.json`,
|
|
596
|
+
2. the bookkeeping files inside the installed tree (`node_modules/.pnpm`,
|
|
597
|
+
`.yarn-state.yml`, `.package-lock.json`) — whoever built what is actually on disk,
|
|
598
|
+
3. the most recently written lockfile.
|
|
599
|
+
|
|
600
|
+
For Python, uv or Poetry takes the environment whenever it recognises the project —
|
|
601
|
+
between the two, whichever one's lockfile is actually on disk wins — and the
|
|
602
|
+
`requirements.txt` adapter handles everything else.
|
|
603
|
+
|
|
604
|
+
---
|
|
605
|
+
|
|
606
|
+
## Configuration
|
|
607
|
+
|
|
608
|
+
Global settings live in `%APPDATA%\dev-prune` (Windows),
|
|
609
|
+
`~/Library/Application Support/dev-prune` (macOS) and `$XDG_CONFIG_HOME/dev-prune`
|
|
610
|
+
(Linux). `devp config wizard` opens all of them in a full-screen configurator, and runs itself
|
|
611
|
+
once on a first install — so the defaults are something you agreed to rather than
|
|
612
|
+
inherited — and again after an upgrade adds a setting you have never been shown.
|
|
613
|
+
|
|
614
|
+
| Key | Default | Meaning |
|
|
615
|
+
| :--------------------------------------------------------------------------------- | :-------: | :---------------------------------------------------------------------------------- |
|
|
616
|
+
| `idle_days` | `15` | How long a repository must be untouched to become a candidate |
|
|
617
|
+
| `min_size_mb` | `0` | Smallest bloat directory worth deleting; `0` disables the floor |
|
|
618
|
+
| `scan_depth` | `6` | Levels below a repository root that discovery descends |
|
|
619
|
+
| `require_confirmation` | `true` | Whether a pass asks before deleting |
|
|
620
|
+
| `allow_manifest_rewrite` | `false` | Whether verification may *repair* a drifted lockfile instead of refusing |
|
|
621
|
+
| `command_timeout_secs` | `600` | Ceiling on any one package manager command |
|
|
622
|
+
| `auto_setup` · `auto_daemon` · `auto_hooks` | `true` | Whether the integration pass may run unattended, and what it may install |
|
|
623
|
+
| `auto_hooks_chain` | `false` | Whether it may take a `core.hooksPath` another tool holds, forwarding every hook on |
|
|
624
|
+
| `check_interval_days` | `2` | How often the OS scheduler runs a pass |
|
|
625
|
+
| `update_check` | `true` | Whether the periodic release check runs |
|
|
626
|
+
| `update_check_interval_days` · `update_check_timeout_secs` | `7` · `5` | Minimum gap between checks, and how long one may hang |
|
|
627
|
+
| `enable_cargo` · `enable_gradle` · `enable_maven` · `enable_swift` · `enable_dart` · `enable_mix_build` | `false` | Turn on an opt-in build-tool adapter; `build_idle_days` (`45`) gates all six |
|
|
628
|
+
| `adapter_idle_days` | *(none)* | Per-adapter idle floors, as `cargo=90,npm=30` — each raises only its own window |
|
|
629
|
+
| `disabled_adapters` | *(none)* | Adapters to leave alone entirely, by name — as if that ecosystem were not installed |
|
|
630
|
+
|
|
631
|
+
Three of them — `idle_days` (as `override_idle_days`), `min_size_mb` and `scan_depth` —
|
|
632
|
+
also take a per-repository form in that project's `.devprune.json`, where they win for
|
|
633
|
+
that tree only. The rest are deliberately global: a project can commit its
|
|
634
|
+
`.devprune.json`, and a repository you have never read should not be able to grant itself
|
|
635
|
+
permission to have its manifests rewritten during an unattended pass.
|
|
636
|
+
|
|
637
|
+
An out-of-range value is rejected with the range in the message rather than silently
|
|
638
|
+
clamped. `scan_depth` included: `config set` accepts `1`–`32` and refuses anything else
|
|
639
|
+
outright — the clamp to that range survives only as the backstop for a hand-edited
|
|
640
|
+
config file.
|
|
641
|
+
|
|
642
|
+
---
|
|
643
|
+
|
|
644
|
+
## Background automation
|
|
645
|
+
|
|
646
|
+
Installation registers an OS-native scheduler — Windows Task Scheduler, a macOS
|
|
647
|
+
LaunchAgent, or a systemd user timer — that runs a pass every `check_interval_days`, plus
|
|
648
|
+
non-blocking `post-commit`, `post-checkout` and `post-merge` Git hooks that register new
|
|
649
|
+
repositories as you visit them. Both are reinstated after an upgrade if anything went
|
|
650
|
+
missing.
|
|
651
|
+
|
|
652
|
+
```bash
|
|
653
|
+
devp setup --status # what is installed, what is not, and why
|
|
654
|
+
devp config set auto_setup false # stop the unattended pass entirely
|
|
655
|
+
devp uninstall # remove the scheduler, hooks and the devp link
|
|
656
|
+
```
|
|
657
|
+
|
|
658
|
+
Git allows exactly one global `core.hooksPath`, so a tool holding it shuts every other one
|
|
659
|
+
out machine-wide. `devp hook install --chain` takes the slot and forwards each hook on to
|
|
660
|
+
the tool it displaced — husky, pre-commit and lefthook keep firing, in order, with their
|
|
661
|
+
own exit codes. It is opt-in, because rewiring another tool's Git configuration unasked is
|
|
662
|
+
not something an install should do.
|
|
663
|
+
|
|
664
|
+
Full decision flow: [docs/BACKGROUND_AUTOMATION.md](docs/BACKGROUND_AUTOMATION.md).
|
|
665
|
+
|
|
666
|
+
---
|
|
667
|
+
|
|
668
|
+
## How it compares
|
|
669
|
+
|
|
670
|
+
| | `dev-prune` | `npkill` | `cargo-clean-all` | `pyclean` | `git clean` | `dust` / `ncdu` | BleachBit |
|
|
671
|
+
| :---------------------------------------- | :-------------------------: | :------: | :---------------: | :-------: | :-------------: | :-------------: | :-------: |
|
|
672
|
+
| Ecosystems | **JS/TS, Python, Rust, Go** | Node | Rust | Python | untracked files | — | OS caches |
|
|
673
|
+
| Many projects per repository | **✓** | ✗ | ✗ | ✗ | n/a | n/a | ✗ |
|
|
674
|
+
| `.git` boundary enforced | **✓** | ✗ | ✓ | ✗ | ✓ | ✗ | ✗ |
|
|
675
|
+
| Lockfile verified before deleting | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
|
|
676
|
+
| Commit log **and** `mtime` activity check | **✓** | ✗ | `mtime` only | ✗ | ✗ | ✗ | ✗ |
|
|
677
|
+
| One-command restore | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
|
|
678
|
+
| Undo the last pass | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
|
|
679
|
+
| Background scheduler | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
|
|
680
|
+
| Git hook auto-registration | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
|
|
681
|
+
| Per-repository config + 0ms opt-out | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
|
|
682
|
+
| Machine-readable `--json` | **✓** | ✗ | ✗ | ✗ | ✗ | partial | ✗ |
|
|
683
|
+
| AI agent skill | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
|
|
684
|
+
| Runtime required | **none** (static binary) | Node.js | none | Python | none | none | Python |
|
|
685
|
+
|
|
686
|
+
Longer analysis: [docs/MARKET_ANALYSIS.md](docs/MARKET_ANALYSIS.md).
|
|
687
|
+
|
|
688
|
+
---
|
|
689
|
+
|
|
690
|
+
## Architecture
|
|
691
|
+
|
|
692
|
+
```mermaid
|
|
693
|
+
flowchart TD
|
|
694
|
+
UserCLI["CLI / TUI Interface<br/>(devp / dev-prune)"] --> Registry["Global Registry<br/>(~/.config/dev-prune/registry.json)"]
|
|
695
|
+
UserCLI --> Engine["Prune Engine"]
|
|
696
|
+
|
|
697
|
+
Engine --> FastIgnore{ignore.devprune.json?}
|
|
698
|
+
FastIgnore -->|Exists| Skip["Skip Repo O(1) 0ms"]
|
|
699
|
+
FastIgnore -->|Missing| PerRepoConfig["Read .devprune.json"]
|
|
700
|
+
|
|
701
|
+
PerRepoConfig --> GitScanner["Git Scanner & Activity Solver<br/>(.git commits + mtime fallback)"]
|
|
702
|
+
Engine --> PreCheck["Required Ecosystem Binary Pre-Checker"]
|
|
703
|
+
Engine --> Adapters["Multi-Ecosystem Adapters"]
|
|
704
|
+
|
|
705
|
+
Adapters --> NPM["npm (package-lock.json -> node_modules)"]
|
|
706
|
+
Adapters --> PNPM["pnpm (pnpm-lock.yaml -> node_modules)"]
|
|
707
|
+
Adapters --> Yarn["yarn (yarn.lock -> node_modules)"]
|
|
708
|
+
Adapters --> Bun["bun (bun.lock -> node_modules)"]
|
|
709
|
+
Adapters --> UV["uv (uv.lock -> .venv)"]
|
|
710
|
+
Adapters --> Venv["venv (requirements.txt -> venv)"]
|
|
711
|
+
Adapters --> Cargo["cargo (Cargo.lock -> target)"]
|
|
712
|
+
Adapters --> Go["go (go.sum -> vendor)"]
|
|
713
|
+
|
|
714
|
+
Adapters --> LockfileCheck{"Lockfile Verification<br/>& Two-Tier Sync"}
|
|
715
|
+
LockfileCheck -->|Success / Present| Prune["Safe Deletion of Bloat Dirs"]
|
|
716
|
+
LockfileCheck -->|Failed & Missing| Abort["Abort Deletion & Log Fix Snippet"]
|
|
717
|
+
|
|
718
|
+
Daemon["OS Background Daemon Scheduler<br/>(Task Scheduler / LaunchAgent / systemd)"] -->|Every 2 Days| Engine
|
|
719
|
+
GitHooks["Git Auto-Registration Hooks<br/>(post-commit / post-checkout / post-merge)"] -->|On Git Activity| Registry
|
|
720
|
+
```
|
|
721
|
+
|
|
722
|
+
- **Registry** — Serde-backed, written atomically, holding registered paths and settings.
|
|
723
|
+
- **Engine** — coordinates activity discovery, verification and space calculation.
|
|
724
|
+
- **FastIgnore** — presence check for `ignore.devprune.json`; no read, no parse.
|
|
725
|
+
- **GitScanner** — `git log` timestamps plus source-file `mtime`.
|
|
726
|
+
- **PreCheck** — confirms the package manager binaries a pass will actually need.
|
|
727
|
+
- **Adapters** — one per ecosystem, each owning detection, verification and restore.
|
|
728
|
+
- **LockfileCheck** — the gate; failure aborts the deletion and prints the exact fix command.
|
|
729
|
+
- **Daemon / GitHooks** — the unattended pass, and registration as you work.
|
|
730
|
+
|
|
731
|
+
Deeper: [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) ·
|
|
732
|
+
[HLD](docs/architecture/HLD.md) · [LLD](docs/architecture/LLD.md).
|
|
733
|
+
|
|
734
|
+
---
|
|
735
|
+
|
|
736
|
+
## Documentation
|
|
737
|
+
|
|
738
|
+
| | |
|
|
739
|
+
| :------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------- |
|
|
740
|
+
| [Documentation hub](docs/README.md) | Index of everything below |
|
|
741
|
+
| [CLI reference](docs/CLI_REFERENCE.md) | Every command, flag, setting, exit code and `--json` document |
|
|
742
|
+
| [Safety invariants](docs/SAFETY_INVARIANTS.md) | The seven guarantees, and why each exists |
|
|
743
|
+
| [Architecture](docs/ARCHITECTURE.md) · [HLD](docs/architecture/HLD.md) · [LLD](docs/architecture/LLD.md) | How it is built |
|
|
744
|
+
| [Background automation](docs/BACKGROUND_AUTOMATION.md) | Schedulers, hooks, chaining, and turning it all off |
|
|
745
|
+
| [IDE & editor integration](docs/IDE_INTEGRATION.md) | The extension, schema IntelliSense, and every editor it works in |
|
|
746
|
+
| [Adding an adapter](docs/ADDING_ADAPTERS.md) | End-to-end tutorial for a new ecosystem |
|
|
747
|
+
| [Releases & manual install](docs/RELEASES_AND_MANUAL_INSTALL.md) · [Distribution](docs/DISTRIBUTION.md) | Every install channel, and building from source |
|
|
748
|
+
| [Troubleshooting](docs/troubleshooting/README.md) | Symptom-first, with the fix for each |
|
|
749
|
+
| [Privacy](docs/PRIVACY.md) | The one network request, in full |
|
|
750
|
+
| [Market analysis](docs/MARKET_ANALYSIS.md) | Where this sits among the alternatives |
|
|
751
|
+
| [Contributing](CONTRIBUTING.md) · [Security policy](SECURITY.md) · [Changelog](CHANGELOG.md) | |
|
|
752
|
+
|
|
753
|
+
---
|
|
754
|
+
|
|
755
|
+
## License & privacy
|
|
756
|
+
|
|
757
|
+
Copyright 2026 [VKrishna04](https://vkrishna04.me). Licensed under the Apache License,
|
|
758
|
+
Version 2.0 — see [LICENSE.md](LICENSE.md). Every source file carries an
|
|
759
|
+
[SPDX](https://spdx.dev/) identifier, so automated licence scanners see the same
|
|
760
|
+
answer the file header does.
|
|
761
|
+
|
|
762
|
+
> [!IMPORTANT]
|
|
763
|
+
> **No analytics, no diagnostics, no usage data** — none collected, none sent. Your
|
|
764
|
+
> workspace structure, directory paths and repository names never leave the machine.
|
|
765
|
+
>
|
|
766
|
+
> `dev-prune` makes exactly one network request: an unauthenticated `GET` to GitHub's
|
|
767
|
+
> public releases endpoint, to tell you when a newer version exists. It has no body,
|
|
768
|
+
> carries no identifier, and runs at most once a week. Turn it off with `devp config set
|
|
769
|
+
> update_check false`. Full detail in [docs/PRIVACY.md](docs/PRIVACY.md).
|
package/bin/dev-prune
CHANGED
|
Binary file
|
package/package.json
CHANGED
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "dev-prune-linux-arm64",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.7.0",
|
|
4
4
|
"description": "Prebuilt dev-prune binary for linux arm64. Installed automatically by the 'dev-prune' package; not meant to be depended on directly.",
|
|
5
5
|
"os": ["linux"],
|
|
6
6
|
"cpu": ["arm64"],
|
|
7
|
-
"files": ["bin", "LICENSE.md"],
|
|
7
|
+
"files": ["bin", "LICENSE.md", "README.md"],
|
|
8
8
|
"license": "Apache-2.0",
|
|
9
9
|
"author": "VKrishna04",
|
|
10
10
|
"homepage": "https://devprune.vkrishna04.me",
|