npkill
List any node_modules 📦 dir in your system and how heavy they are. You can then select which ones you want to erase to free up space 🧹
Runssource: GitHubhomepageTypeScriptMITcommit 2dad63647fdd
TypeScript, MIT licensed. The project labels itself: cli, command line, developer tools, hacktoberfest, javascript, module, node and nodejs.
npkill runs. An Argusic agent installed it in 2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npkill v0.12.2 installs, builds, passes all 236 tests, and correctly scans for node_modules directories returning valid JSON output.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Missing devDependency 'tsconfig-paths' caused 'npm run start' to fail with MODULE_NOT_FOUND1 minute
- Install time
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- node lib/index.js --version returned v0.12.2; node lib/index.js -d /tmp/npkill-verify --json returned {resultsCount:2}; npm test: 236 passed, 19 suites
- Model tokens used
- 65,964
- Exact commit tested
- 2dad63647fdd
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `node ./lib/index.js -d /tmp/npkill-verify --json` → found 2 `node_modules` dirs, returned valid … - `npm run start -- --version` → `v0.12.2` (after fix) tokens used 65,964 All good — build, tests, and CLI invocation all work. Here's the final report: **Install & build:** `npm install` completed successfully (962 packages, engine warnings only for o… **Error found & fixed:** The `npm run start` dev script referenced `tsconfig-paths/register` which … **Verification:** - `node ./lib/index.js --version` → `v0.12.2` - `npm test` → 19 suites passed, 236 tests passed, 12 skipped - `node ./lib/index.js -d /tmp/npkill-verify --json` → found 2 `node_modules` dirs, returned valid … - `npm run start -- --version` → `v0.12.2` (after fix)
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 2 minutes, faster than the median of the 24 comparable projects Argusic has measured.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 25 cli projects Argusic has installed and timed, npkill was the 6th fastest to reach a running state, and 23 of 25 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
clicommand-linedeveloper-toolshacktoberfestjavascriptmodulenodenodejsnpmtooltypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/npkill)Questions
- Does npkill run?
- Yes. npkill runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test npkill?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2dad63647fdd. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test npkill?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does npkill take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does npkill need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing npkill?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does npkill compare with the alternatives?
- Of the 25 cli projects Argusic has installed and timed, npkill was the 6th fastest to reach a running state, and 23 of 25 reached one at all.
- Where is the evidence for npkill?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.