dev-prune 1.0.0__py3-none-win_amd64.whl

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.
Binary file
@@ -0,0 +1,581 @@
1
+ Metadata-Version: 2.1
2
+ Name: dev-prune
3
+ Version: 1.0.0
4
+ Summary: Universal, lockfile-safe workspace pruner. Reclaims disk space from idle Git repositories by deleting only dependency and build directories a lockfile can rebuild.
5
+ Author: VKrishna04
6
+ License: Apache-2.0
7
+ Keywords: cli,cleanup,disk-space,node_modules,venv,monorepo,workspace,prune
8
+ Project-URL: Homepage, https://devprune.vkrishna04.me
9
+ Project-URL: Documentation, https://github.com/Life-Experimentalist/dev-prune/blob/main/docs/README.md
10
+ Project-URL: Source, https://github.com/Life-Experimentalist/dev-prune
11
+ Project-URL: Issues, https://github.com/Life-Experimentalist/dev-prune/issues
12
+ Project-URL: Changelog, https://github.com/Life-Experimentalist/dev-prune/blob/main/CHANGELOG.md
13
+ Classifier: Development Status :: 5 - Production/Stable
14
+ Classifier: Environment :: Console
15
+ Classifier: Intended Audience :: Developers
16
+ Classifier: License :: OSI Approved :: Apache Software License
17
+ Classifier: Operating System :: MacOS
18
+ Classifier: Operating System :: Microsoft :: Windows
19
+ Classifier: Operating System :: POSIX :: Linux
20
+ Classifier: Programming Language :: Rust
21
+ Classifier: Topic :: Software Development :: Build Tools
22
+ Classifier: Topic :: System :: Filesystems
23
+ Classifier: Topic :: Utilities
24
+ Requires-Python: >=3.8
25
+ Description-Content-Type: text/markdown
26
+
27
+ <div align="center">
28
+
29
+ ```text
30
+ ___ _____ __ __ ____ ____ _ _ _ _ _____
31
+ | _ \ | ____|\ \ / / | _ \| _ \| | | | \ | | ____|
32
+ | | | || _| \ \ / / | |_) | |_) | | | | \| | _|
33
+ | |_| || |___ \ V / | __/| _ <| |_| | |\ | |___
34
+ |____/ |_____| \_/ |_| |_| \_\\___/|_| \_|_____| v1.0.0
35
+ ```
36
+
37
+ # `dev-prune` &nbsp;·&nbsp; `devp`
38
+
39
+ >**Reclaim the disk space your idle repositories are sitting on — without ever deleting
40
+ something a lockfile cannot put back.**
41
+
42
+ [![CI](https://github.com/Life-Experimentalist/dev-prune/actions/workflows/ci.yml/badge.svg)](https://github.com/Life-Experimentalist/dev-prune/actions/workflows/ci.yml) | [![Pages](https://github.com/Life-Experimentalist/dev-prune/actions/workflows/pages.yml/badge.svg)](https://devprune.vkrishna04.me/) | [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/LICENSE.md) | [![Rust](https://img.shields.io/badge/rust-1.85%2B-orange.svg)](https://www.rust-lang.org/) | [![Platforms](https://img.shields.io/badge/platforms-Windows%20%7C%20macOS%20%7C%20Linux-lightgrey.svg)](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/RELEASES_AND_MANUAL_INSTALL.md)
43
+
44
+ [**Website**](https://devprune.vkrishna04.me/) · [**Documentation**](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/README.md) · [**CLI reference**](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/CLI_REFERENCE.md) · [**Safety invariants**](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/SAFETY_INVARIANTS.md) · [**Changelog**](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/CHANGELOG.md)
45
+
46
+ <img src="https://raw.githubusercontent.com/Life-Experimentalist/dev-prune/v1.0.0/assets/hero_banner.png" alt="dev-prune" width="820" />
47
+
48
+ </div>
49
+
50
+ ---
51
+
52
+ `node_modules`, `.venv`, `target` and `vendor` are the largest directories on most
53
+ developers' machines, and the least valuable: every byte in them is described by a
54
+ lockfile that is already committed. A project you have not opened since March is holding
55
+ gigabytes hostage for a build you are not running.
56
+
57
+ `dev-prune` finds those directories across every Git repository you register, and deletes
58
+ them — but only after proving the exact command that puts them back would succeed. It is
59
+ a single Rust binary, installs its own background schedule, and answers to two names:
60
+ `dev-prune` and `devp`.
61
+
62
+ > [!IMPORTANT]
63
+ > **The rule the whole tool is built around:** nothing is deleted unless dev-prune has
64
+ > just verified, read-only, that its lockfile can rebuild it. There is no flag to skip
65
+ > that check. `--ignore-idle` lifts the idle-day wait and *nothing else*.
66
+
67
+ ---
68
+
69
+ ## Contents
70
+
71
+ [Install](#install) · [60-second tour](#60-second-tour) · [What it looks like](#what-it-looks-like) ·
72
+ [Why it is safe](#why-it-is-safe) · [Features](#features) · [Commands](#commands) ·
73
+ [Ecosystems](#supported-ecosystems) · [Monorepos](#repositories-with-more-than-one-ecosystem) ·
74
+ [Configuration](#configuration) · [Automation](#background-automation) ·
75
+ [Comparison](#how-it-compares) · [Architecture](#architecture) · [Docs](#documentation)
76
+
77
+ ---
78
+
79
+ ## Install
80
+
81
+ ### One-liner
82
+
83
+ ```bash
84
+ curl -fsSL https://devprune.vkrishna04.me/install.sh | sh
85
+ ```
86
+
87
+ ```powershell
88
+ iwr -useb https://devprune.vkrishna04.me/install.ps1 | iex
89
+ ```
90
+
91
+ Downloads the prebuilt binary for your platform, verifies its published SHA-256, puts it
92
+ on `PATH`, and runs `dev-prune setup`. Pass `--no-auto-setup` / `-NoAutoSetup` to skip
93
+ that last step.
94
+
95
+ ### From a package manager
96
+
97
+ ```bash
98
+ npx dev-prune status # no install at all
99
+ npm install -g dev-prune
100
+ uv tool install dev-prune # or: uvx dev-prune status
101
+ pipx install dev-prune
102
+ pip install dev-prune
103
+ cargo binstall dev-prune # fetches the prebuilt release archive
104
+ cargo install dev-prune # builds from source, needs Rust 1.85+
105
+ ```
106
+
107
+ The npm and PyPI packages **contain the binary** — there is no `postinstall` download
108
+ step, so they work under `npm ci --ignore-scripts`, behind a registry mirror, and
109
+ offline. Everything but `cargo install` ships a prebuilt executable.
110
+
111
+ crates.io stores source and nothing else, so `cargo install` has no binary to fetch and
112
+ always compiles. [`cargo binstall`](https://github.com/cargo-bins/cargo-binstall) is the
113
+ one that downloads: `Cargo.toml` tells it where this project's release archives live, so
114
+ it unpacks the same executable the installers use, with no toolchain involved.
115
+
116
+ ### Direct download
117
+
118
+ Six checksummed archives per release on
119
+ [GitHub Releases](https://github.com/Life-Experimentalist/dev-prune/releases) — Windows,
120
+ macOS and Linux, x64 and arm64. The Linux binaries are statically linked against musl, so
121
+ one file per architecture runs on every distribution including Alpine.
122
+
123
+ Manual install and build-from-source:
124
+ [docs/RELEASES_AND_MANUAL_INSTALL.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/RELEASES_AND_MANUAL_INSTALL.md).
125
+ Every channel in detail: [docs/DISTRIBUTION.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/DISTRIBUTION.md).
126
+
127
+ > [!TIP]
128
+ > **`devp` is a real executable, not a shell alias.** Installation puts a second binary
129
+ > next to `dev-prune`, so the short name works in cmd, PowerShell, bash, fish, an IDE
130
+ > terminal and a scheduled task alike — with no profile to re-source, and no chance of an
131
+ > upgrade leaving `devp` on the old version.
132
+
133
+ ---
134
+
135
+ ## 60-second tour
136
+
137
+ ```bash
138
+ devp init ~/Projects # register every Git repository under a tree
139
+ devp status # dashboard: what is tracked, what is reclaimable
140
+ devp run --dry-run # what a pass would delete — changes nothing
141
+ devp run # do it, after confirming
142
+ devp restore --last-run # put back exactly what that pass deleted
143
+ ```
144
+
145
+ Three more worth knowing on day one:
146
+
147
+ ```bash
148
+ devp caches # every package manager cache, sized. Deletes nothing
149
+ devp doctor . # why is this repository not being pruned?
150
+ devp -V # version, OS, architecture, config path, PATH audit
151
+ ```
152
+
153
+ ---
154
+
155
+ ## What it looks like
156
+
157
+ <details open>
158
+ <summary><b><code>devp run --dry-run</code></b> — the plan, before anything is touched</summary>
159
+
160
+ ```console
161
+ $ devp run --dry-run
162
+
163
+ dev-prune run (DRY RUN)
164
+ → Scanning 4 registered repositories for prune candidates...
165
+
166
+ Prune Candidates & Space Savings Calculation
167
+ → • ~/Code/acme-api → node_modules (412.7 MiB) [pnpm]
168
+ → • ~/Code/acme-api → services/worker/.venv (188.2 MiB) [uv]
169
+ → • ~/Code/render-farm → target (2.14 GiB) [cargo]
170
+ → • ~/Code/edge-proxy → vendor (96.4 MiB) [go]
171
+
172
+ Summary (Dry Run)
173
+ → Would free 2.82 GiB across 4 bloat directories.
174
+ ```
175
+
176
+ </details>
177
+
178
+ <details>
179
+ <summary><b><code>devp status</code></b> — the dashboard, or a plain table with no TTY</summary>
180
+
181
+ ```console
182
+ $ devp status
183
+
184
+ → Global Config Location: ~/.config/dev-prune/registry.json
185
+ → Background OS Daemon: Installed
186
+ → Background Git Hooks: Installed
187
+ → Global Command Timeout: 600s (10m)
188
+ → Tracked Repositories: 4
189
+ → Historical Space Saved: 6.31 GiB across 9 prune passes
190
+
191
+ dev-prune status
192
+
193
+ # Repository Status / Reason Adapters Bloat Last Activity Last Pruned
194
+ ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
195
+ 1 acme-api Candidate pnpm+uv 600.9 MiB 2026-04-02 Never
196
+ 2 render-farm Candidate cargo 2.14 GiB 2026-03-11 2026-01-08
197
+ 3 edge-proxy Candidate go 96.4 MiB 2026-05-19 Never
198
+ 4 dashboard Active (not idle) npm 314.0 MiB 2026-08-12 2026-06-30
199
+ ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
200
+ → Total: 4 repos | 3 candidates | 3.13 GiB reclaimable
201
+ ```
202
+
203
+ Keys: `↑`/`↓` move, `p` pre-selects every candidate, `Space` deselects the one you are
204
+ keeping, `Enter` prunes the rest, `i` toggles ignore for a repository, `q` exits.
205
+
206
+ </details>
207
+
208
+ <details>
209
+ <summary><b><code>devp caches</code></b> — where the rest of the disk went</summary>
210
+
211
+ ```console
212
+ $ devp caches
213
+
214
+ Package manager caches
215
+
216
+ uv cache 16.25 GiB ~/.cache/uv
217
+ clear: uv cache prune
218
+
219
+ npm cache 8.97 GiB ~/.npm
220
+ clear: npm cache clean --force
221
+
222
+ go build cache 371.75 MiB ~/.cache/go-build
223
+ clear: go clean -cache
224
+ compiled build artifacts; clearing them means the next build is a cold one
225
+
226
+ cargo registry sources 104.75 MiB ~/.cargo/registry/src
227
+ clear: rm -rf ~/.cargo/registry/src
228
+ unpacked copies of the archives above; cargo re-extracts these offline
229
+
230
+ … (pip, bun, pnpm, go module cache, cargo registry cache)
231
+
232
+ Total 27.26 GiB across 9 caches
233
+
234
+ → Nothing above was deleted, and dev-prune never deletes any of it.
235
+ ```
236
+
237
+ A cache lives outside every repository and is shared by all of them, so no single
238
+ lockfile can prove it recoverable — and it is what makes `devp restore` fast. `devp
239
+ caches` reports and prints the clear command; running it is your decision.
240
+
241
+ </details>
242
+
243
+ <details>
244
+ <summary><b><code>devp doctor .</code></b> — the one reason a repository is being skipped</summary>
245
+
246
+ ```console
247
+ $ devp doctor .
248
+
249
+ dev-prune doctor (~/Code/dashboard)
250
+
251
+ Repository
252
+ Git repository ✓ yes
253
+ Registered ✓ yes, since 2026-04-11
254
+ .devprune.json parses; idle_days 20
255
+ Opt-out none
256
+ Activity 2026-08-12 (0 days ago), threshold 20 — active
257
+ Size floor none — every recognised directory counts
258
+ Scan depth 6 levels below the root
259
+
260
+ Projects
261
+
262
+ . (npm)
263
+ Lockfile ✓ package-lock.json present
264
+ Bloat ✓ node_modules (314.0 MiB)
265
+
266
+ Verdict
267
+ ✗ Would `devp run` prune this? No — active within the last 20 days.
268
+ `devp --ignore-idle run ~/Code/dashboard` overrides exactly that check and nothing else.
269
+ ```
270
+
271
+ It runs no package manager and repairs nothing, so it is safe to run twice — once to see
272
+ the problem, once to confirm the fix. Without a path it audits the installation instead:
273
+ binary location and `PATH`, the registry and every setting in it, the integrations, which
274
+ package managers are reachable, and the release-check state.
275
+
276
+
277
+
278
+ </details>
279
+
280
+ ---
281
+
282
+ ## Why it is safe
283
+
284
+ Seven invariants, enforced in code rather than by convention, none of which has a bypass
285
+ flag. Full detail and the reasoning behind each in
286
+ [docs/SAFETY_INVARIANTS.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/SAFETY_INVARIANTS.md).
287
+
288
+ | # | Invariant | What it prevents |
289
+ | :---: | :-------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------ |
290
+ | 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 |
291
+ | 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 |
292
+ | 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 |
293
+ | 4 | **Atomic state writes** — write to a temp file, then rename | A registry corrupted by a crash or a power cut mid-write |
294
+ | 5 | **0ms ignore fast path** — `ignore.devprune.json` short-circuits before any parsing | A repository you opted out of being scanned at all |
295
+ | 6 | **Symlink and junction refusal** | Following a link out of the repository and deleting storage it does not own |
296
+ | 7 | **Nested repository boundary** | A submodule being deleted as part of its parent instead of on its own terms |
297
+
298
+ Verification is **read-only by default**: `npm ci --dry-run`, `uv lock --locked`, `cargo
299
+ metadata --locked`, `go mod download`. Each resolves the dependency graph against the
300
+ lockfile on disk and *fails* when the two disagree, instead of quietly rewriting the
301
+ lockfile and continuing. The writing form runs in exactly two cases — when no lockfile
302
+ exists at all, and when you have asked with `devp config set allow_manifest_rewrite true`
303
+ — because a pass can be started by the OS scheduler while you are away, and a background
304
+ process that leaves a dirty working tree is a surprise.
305
+
306
+ ---
307
+
308
+ ## Features
309
+
310
+ | | |
311
+ | :-------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
312
+ | 🔒 **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` |
313
+ | 🧩 **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 |
314
+ | ↩️ **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 |
315
+ | 🕒 **Activity-aware** | Combines `git log` timestamps with source-file `mtime`, so uncommitted work protects a repository just as a commit does |
316
+ | 📊 **Cache report** | `devp caches` sizes every package manager cache and store on the machine and prints the command that clears each. Read-only, always |
317
+ | 🩺 **`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 |
318
+ | 🤖 **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 |
319
+ | ⚡ **0ms opt-out** | An `ignore.devprune.json` in a repository root is honoured by file presence alone — no read, no parse |
320
+ | 🔌 **`--json` on every reporting command** | `run`, `status` and `caches` each emit one versioned document on stdout, diagnostics on stderr. Built for scripts and agents |
321
+ | 🧠 **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 |
322
+ | 🖼️ **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 |
323
+ | 🚫 **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 |
324
+
325
+ ---
326
+
327
+ ## Commands
328
+
329
+ | Command | Also | What it does |
330
+ | :--------------------- | :------------------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------ |
331
+ | `devp init [PATHS]` | `scan`, `onboard` | Crawls directory trees for Git repositories and registers them, then runs the `setup` integration pass |
332
+ | `devp link [PATH]` | | Registers one repository |
333
+ | `devp unlink [PATH]` | `--missing` | Unregisters one; `--missing` drops every entry whose directory is gone, in one pass |
334
+ | `devp undo` | | Reverts the most recent `init` or `link` |
335
+ | `devp run [PATH]` | `--dry-run`, `--only`, `--skip`, `--except`, `--min-size`, `--json` | Prunes every registered repository, or one target |
336
+ | `devp status` | `--json` | Interactive dashboard; a plain table when there is no TTY |
337
+ | `devp caches` | `--json` | Sizes every package manager cache on the machine and prints the command that clears each. **Deletes nothing** |
338
+ | `devp restore [PATH]` | `--last-run` | Reinstalls dependencies for every project in a tree; `--last-run` undoes the last prune pass |
339
+ | `devp doctor [PATH]` | | Diagnoses the installation, or one repository — ending with the single reason a pass would or would not touch it |
340
+ | `devp config [ACTION]` | `get`, `set`, `show`, `wizard`, `project`, `daemon`, `hook`, `icon` | Global settings, per-repository `.devprune.json`, scheduler, Git hooks, file manager icons |
341
+ | `devp setup` | `--status` | Installs any missing integration; `--status` only reports |
342
+ | `devp update` | `--offline` | Prints the installed version, checks GitHub for a newer release, shows the upgrade command for your install channel |
343
+ | `devp skill` | | Exports `SKILL.md` and prints AI agent onboarding prompts |
344
+ | `devp uninstall` | `--deep` | Removes the scheduler, hooks and the `devp` link; `--deep` also clears configuration |
345
+ | `devp -V` | | Version plus an environment audit: OS, architecture, config path, PATH activation |
346
+
347
+ `devp hook`, `devp daemon` and `devp icon` are shorthands for the `config` subcommands of
348
+ the same name, and `install` / `uninstall` / `on` / `off` work wherever `enable` /
349
+ `disable` do — so `devp hook install` and `devp config hook enable` are the same command.
350
+ A misspelled action is rejected rather than quietly reported as status.
351
+
352
+ Exit codes are a contract: `0` success, `1` failure, `2` unusable arguments. Full flag
353
+ list, every setting and the `--json` schema: **[docs/CLI_REFERENCE.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/CLI_REFERENCE.md)**.
354
+
355
+ ---
356
+
357
+ ## Supported ecosystems
358
+
359
+ Adapters detect the project, verify the lockfile, and own the bloat directories:
360
+
361
+ | Ecosystem | Detected by | Bloat | Verification (read-only) | Restore |
362
+ | :---------------- | :------------------------------------------------------- | :-------------------------------------- | :---------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------- |
363
+ | **npm** | `package-lock.json` | `node_modules` | `npm ci --dry-run --ignore-scripts` | `npm ci` |
364
+ | **pnpm** | `pnpm-lock.yaml` | `node_modules` | `pnpm install --lockfile-only --frozen-lockfile` | `pnpm install --frozen-lockfile` |
365
+ | **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` |
366
+ | **Bun** | `bun.lockb`, `bun.lock` | `node_modules` | `bun install --frozen-lockfile --dry-run --ignore-scripts` | `bun install --frozen-lockfile` |
367
+ | **uv** (Python) | `uv.lock`, `[tool.uv]` in `pyproject.toml` | `.venv` | `uv lock --locked` | `uv sync` |
368
+ | **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` |
369
+ | **Cargo** (Rust) | `Cargo.toml` | `target` | `cargo metadata --locked` | *(rebuilt by the next `cargo build`)* |
370
+ | **Go** | `go.mod` | `vendor` | `go mod download` | `go mod vendor` |
371
+
372
+ A required binary that is missing is a reason to skip, never a reason to delete: if `npm`
373
+ is not on `PATH`, the `node_modules` it owns is left exactly where it is.
374
+
375
+ > [!TIP]
376
+ > Adding an ecosystem is documented end to end in
377
+ > [docs/ADDING_ADAPTERS.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/ADDING_ADAPTERS.md) — trait, registration, tests.
378
+
379
+ ### Repositories with more than one ecosystem
380
+
381
+ A repository is not assumed to be one project. dev-prune walks the root and up to
382
+ `scan_depth` levels below it — six by default, `devp config set scan_depth N` to change
383
+ it, or `"scan_depth"` in a repository's `.devprune.json` for just that tree. Every
384
+ directory a package manager recognises is verified and pruned on its own terms. All three
385
+ of these work:
386
+
387
+ ```
388
+ monorepo/ monorepo/ monorepo/
389
+ ├── package-lock.json ├── frontend/ ├── Cargo.toml
390
+ ├── uv.lock │ └── pnpm-lock.yaml ├── web/
391
+ └── Cargo.toml ├── services/api/ │ └── package-lock.json
392
+ │ └── uv.lock └── scripts/
393
+ three managers, one root └── tools/cli/ └── requirements.txt
394
+ └── Cargo.toml
395
+ root + nested, mixed
396
+ one manager per subtree
397
+ ```
398
+
399
+ Results are reported by repository-relative path, so a monorepo reads unambiguously:
400
+
401
+ ```
402
+ • MyMonorepo → frontend/node_modules (412.7 MiB) [pnpm]
403
+ • MyMonorepo → services/api/.venv (188.2 MiB) [uv]
404
+ • MyMonorepo → tools/cli/target (1.4 GiB) [cargo]
405
+ ```
406
+
407
+ The walk never descends into `node_modules`, `target`, `vendor`, virtual environments,
408
+ hidden directories, or nested repositories — a submodule is pruned as itself, never as
409
+ part of its parent.
410
+
411
+ When npm, pnpm, yarn and bun all claim the same `node_modules`, exactly one is chosen,
412
+ strongest signal first:
413
+
414
+ 1. the `packageManager` field in `package.json`,
415
+ 2. the bookkeeping files inside the installed tree (`node_modules/.pnpm`,
416
+ `.yarn-state.yml`, `.package-lock.json`) — whoever built what is actually on disk,
417
+ 3. the most recently written lockfile.
418
+
419
+ For Python, uv takes the environment whenever it recognises the project; the
420
+ `requirements.txt` adapter handles everything else.
421
+
422
+ ---
423
+
424
+ ## Configuration
425
+
426
+ Global settings live in `%APPDATA%\dev-prune` (Windows),
427
+ `~/Library/Application Support/dev-prune` (macOS) and `$XDG_CONFIG_HOME/dev-prune`
428
+ (Linux). `devp config wizard` walks through every one of them and runs itself once on a
429
+ first install, so the defaults are something you agreed to.
430
+
431
+ | Key | Default | Meaning |
432
+ | :--------------------------------------------------------- | :-------: | :---------------------------------------------------------------------------------- |
433
+ | `idle_days` | `15` | How long a repository must be untouched to become a candidate |
434
+ | `min_size_mb` | `0` | Smallest bloat directory worth deleting; `0` disables the floor |
435
+ | `scan_depth` | `6` | Levels below a repository root that discovery descends |
436
+ | `require_confirmation` | `true` | Whether a pass asks before deleting |
437
+ | `allow_manifest_rewrite` | `false` | Whether verification may *repair* a drifted lockfile instead of refusing |
438
+ | `command_timeout_secs` | `600` | Ceiling on any one package manager command |
439
+ | `auto_setup` · `auto_daemon` · `auto_hooks` | `true` | Whether the integration pass may run unattended, and what it may install |
440
+ | `auto_hooks_chain` | `false` | Whether it may take a `core.hooksPath` another tool holds, forwarding every hook on |
441
+ | `check_interval_days` | `2` | How often the OS scheduler runs a pass |
442
+ | `update_check` | `true` | Whether the periodic release check runs |
443
+ | `update_check_interval_days` · `update_check_timeout_secs` | `7` · `5` | Minimum gap between checks, and how long one may hang |
444
+
445
+ Three of them — `idle_days` (as `override_idle_days`), `min_size_mb` and `scan_depth` —
446
+ also take a per-repository form in that project's `.devprune.json`, where they win for
447
+ that tree only. The rest are deliberately global: a project can commit its
448
+ `.devprune.json`, and a repository you have never read should not be able to grant itself
449
+ permission to have its manifests rewritten during an unattended pass.
450
+
451
+ An out-of-range value is rejected with the range in the message rather than silently
452
+ clamped — except `scan_depth`, capped at `32`, because a deeper walk is a performance
453
+ mistake rather than a request that cannot be honoured.
454
+
455
+ ---
456
+
457
+ ## Background automation
458
+
459
+ Installation registers an OS-native scheduler — Windows Task Scheduler, a macOS
460
+ LaunchAgent, or a systemd user timer — that runs a pass every `check_interval_days`, plus
461
+ non-blocking `post-commit`, `post-checkout` and `post-merge` Git hooks that register new
462
+ repositories as you visit them. Both are reinstated after an upgrade if anything went
463
+ missing.
464
+
465
+ ```bash
466
+ devp setup --status # what is installed, what is not, and why
467
+ devp config set auto_setup false # stop the unattended pass entirely
468
+ devp uninstall # remove the scheduler, hooks and the devp link
469
+ ```
470
+
471
+ Git allows exactly one global `core.hooksPath`, so a tool holding it shuts every other one
472
+ out machine-wide. `devp hook install --chain` takes the slot and forwards each hook on to
473
+ the tool it displaced — husky, pre-commit and lefthook keep firing, in order, with their
474
+ own exit codes. It is opt-in, because rewiring another tool's Git configuration unasked is
475
+ not something an install should do.
476
+
477
+ Full decision flow: [docs/BACKGROUND_AUTOMATION.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/BACKGROUND_AUTOMATION.md).
478
+
479
+ ---
480
+
481
+ ## How it compares
482
+
483
+ | | `dev-prune` | `npkill` | `cargo-clean-all` | `pyclean` | `git clean` | `dust` / `ncdu` | BleachBit |
484
+ | :---------------------------------------- | :-------------------------: | :------: | :---------------: | :-------: | :-------------: | :-------------: | :-------: |
485
+ | Ecosystems | **JS/TS, Python, Rust, Go** | Node | Rust | Python | untracked files | — | OS caches |
486
+ | Many projects per repository | **✓** | ✗ | ✗ | ✗ | n/a | n/a | ✗ |
487
+ | `.git` boundary enforced | **✓** | ✗ | ✓ | ✗ | ✓ | ✗ | ✗ |
488
+ | Lockfile verified before deleting | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
489
+ | Commit log **and** `mtime` activity check | **✓** | ✗ | `mtime` only | ✗ | ✗ | ✗ | ✗ |
490
+ | One-command restore | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
491
+ | Undo the last pass | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
492
+ | Background scheduler | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
493
+ | Git hook auto-registration | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
494
+ | Per-repository config + 0ms opt-out | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
495
+ | Machine-readable `--json` | **✓** | ✗ | ✗ | ✗ | ✗ | partial | ✗ |
496
+ | AI agent skill | **✓** | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |
497
+ | Runtime required | **none** (static binary) | Node.js | none | Python | none | none | Python |
498
+
499
+ Longer analysis: [docs/MARKET_ANALYSIS.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/MARKET_ANALYSIS.md).
500
+
501
+ ---
502
+
503
+ ## Architecture
504
+
505
+ ```mermaid
506
+ flowchart TD
507
+ UserCLI["CLI / TUI Interface<br/>(devp / dev-prune)"] --> Registry["Global Registry<br/>(~/.config/dev-prune/registry.json)"]
508
+ UserCLI --> Engine["Prune Engine"]
509
+
510
+ Engine --> FastIgnore{ignore.devprune.json?}
511
+ FastIgnore -->|Exists| Skip["Skip Repo O(1) 0ms"]
512
+ FastIgnore -->|Missing| PerRepoConfig["Read .devprune.json"]
513
+
514
+ PerRepoConfig --> GitScanner["Git Scanner & Activity Solver<br/>(.git commits + mtime fallback)"]
515
+ Engine --> PreCheck["Required Ecosystem Binary Pre-Checker"]
516
+ Engine --> Adapters["Multi-Ecosystem Adapters"]
517
+
518
+ Adapters --> NPM["npm (package-lock.json -> node_modules)"]
519
+ Adapters --> PNPM["pnpm (pnpm-lock.yaml -> node_modules)"]
520
+ Adapters --> Yarn["yarn (yarn.lock -> node_modules)"]
521
+ Adapters --> Bun["bun (bun.lock -> node_modules)"]
522
+ Adapters --> UV["uv (uv.lock -> .venv)"]
523
+ Adapters --> Venv["venv (requirements.txt -> venv)"]
524
+ Adapters --> Cargo["cargo (Cargo.lock -> target)"]
525
+ Adapters --> Go["go (go.sum -> vendor)"]
526
+
527
+ Adapters --> LockfileCheck{"Lockfile Verification<br/>& Two-Tier Sync"}
528
+ LockfileCheck -->|Success / Present| Prune["Safe Deletion of Bloat Dirs"]
529
+ LockfileCheck -->|Failed & Missing| Abort["Abort Deletion & Log Fix Snippet"]
530
+
531
+ Daemon["OS Background Daemon Scheduler<br/>(Task Scheduler / LaunchAgent / systemd)"] -->|Every 2 Days| Engine
532
+ GitHooks["Git Auto-Registration Hooks<br/>(post-commit / post-checkout / post-merge)"] -->|On Git Activity| Registry
533
+ ```
534
+
535
+ - **Registry** — Serde-backed, written atomically, holding registered paths and settings.
536
+ - **Engine** — coordinates activity discovery, verification and space calculation.
537
+ - **FastIgnore** — presence check for `ignore.devprune.json`; no read, no parse.
538
+ - **GitScanner** — `git log` timestamps plus source-file `mtime`.
539
+ - **PreCheck** — confirms the package manager binaries a pass will actually need.
540
+ - **Adapters** — one per ecosystem, each owning detection, verification and restore.
541
+ - **LockfileCheck** — the gate; failure aborts the deletion and prints the exact fix command.
542
+ - **Daemon / GitHooks** — the unattended pass, and registration as you work.
543
+
544
+ Deeper: [docs/ARCHITECTURE.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/ARCHITECTURE.md) ·
545
+ [HLD](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/architecture/HLD.md) · [LLD](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/architecture/LLD.md).
546
+
547
+ ---
548
+
549
+ ## Documentation
550
+
551
+ | | |
552
+ | :------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------ |
553
+ | [Documentation hub](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/README.md) | Index of everything below |
554
+ | [CLI reference](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/CLI_REFERENCE.md) | Every command, flag, setting, exit code and `--json` document |
555
+ | [Safety invariants](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/SAFETY_INVARIANTS.md) | The seven guarantees, and why each exists |
556
+ | [Architecture](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/ARCHITECTURE.md) · [HLD](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/architecture/HLD.md) · [LLD](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/architecture/LLD.md) | How it is built |
557
+ | [Background automation](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/BACKGROUND_AUTOMATION.md) | Schedulers, hooks, chaining, and turning it all off |
558
+ | [Adding an adapter](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/ADDING_ADAPTERS.md) | End-to-end tutorial for a new ecosystem |
559
+ | [Releases & manual install](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/RELEASES_AND_MANUAL_INSTALL.md) · [Distribution](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/DISTRIBUTION.md) | Every install channel, and building from source |
560
+ | [Troubleshooting](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/troubleshooting/README.md) | Symptom-first, with the fix for each |
561
+ | [Privacy](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/PRIVACY.md) | The one network request, in full |
562
+ | [Market analysis](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/MARKET_ANALYSIS.md) | Where this sits among the alternatives |
563
+ | [Contributing](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/CONTRIBUTING.md) · [Security policy](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/SECURITY.md) · [Changelog](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/CHANGELOG.md) | |
564
+
565
+ ---
566
+
567
+ ## License & privacy
568
+
569
+ Copyright 2026 VKrishna04. Licensed under the Apache License, Version 2.0 — see
570
+ [LICENSE.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/LICENSE.md). Every source file carries an
571
+ [SPDX](https://spdx.dev/) identifier, so automated licence scanners see the same
572
+ answer the file header does.
573
+
574
+ > [!IMPORTANT]
575
+ > **No analytics, no diagnostics, no usage data** — none collected, none sent. Your
576
+ > workspace structure, directory paths and repository names never leave the machine.
577
+ >
578
+ > `dev-prune` makes exactly one network request: an unauthenticated `GET` to GitHub's
579
+ > public releases endpoint, to tell you when a newer version exists. It has no body,
580
+ > carries no identifier, and runs at most once a week. Turn it off with `devp config set
581
+ > update_check false`. Full detail in [docs/PRIVACY.md](https://github.com/Life-Experimentalist/dev-prune/blob/v1.0.0/docs/PRIVACY.md).
@@ -0,0 +1,6 @@
1
+ dev_prune-1.0.0.data/scripts/dev-prune.exe,sha256=EVVdwNMfxYtuJ9NW1E7GlgIazpAbaFv00C92Z40glic,4329472
2
+ dev_prune-1.0.0.data/scripts/devp.exe,sha256=EVVdwNMfxYtuJ9NW1E7GlgIazpAbaFv00C92Z40glic,4329472
3
+ dev_prune-1.0.0.dist-info/METADATA,sha256=fQMcA3PQbZXzPsh9mv863qF2PM2VRamLvnVrDexSYHg,42985
4
+ dev_prune-1.0.0.dist-info/WHEEL,sha256=9txr2Tq8Q_8Wssrrz1z8MYYYmFhPu_yYmTOVg9h-lvA,103
5
+ dev_prune-1.0.0.dist-info/licenses/LICENSE.md,sha256=QCex48BwRxWq2zE2T-nUdkK6tS1xOAoQKfTjqcGT-u4,11340
6
+ dev_prune-1.0.0.dist-info/RECORD,,
@@ -0,0 +1,4 @@
1
+ Wheel-Version: 1.0
2
+ Generator: dev-prune build_wheels.py
3
+ Root-Is-Purelib: false
4
+ Tag: py3-none-win_amd64
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 VKrishna04
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.