nub
The fast all-in-one Node.js toolkit
Runssource: GitHubhomepageRustMITcommit e283bac7611a
Rust, MIT licensed. The project labels itself: javascript runtime, node version manager, nodejs, package manager and script runner.
nub runs. An Argusic agent installed it in 32 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
nub v0.9.5 is installed via npm; Rust build produced v0.9.6 locally; can run TypeScript files, package.json scripts, and provision Node versions; Node.js test suite passes 140/142 with nub's bundled Node 26.10.0
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.
- npm install -g @nubjs/nub failed with EACCES permission denied on /usr/local/lib/node_modules1 minute
- Tests failed with system Node v18 (requires >=22)1 minute
- Install time
- 32 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- nub --version → v0.9.5, nub /tmp/test-nub.ts printed 'hello from nub!', nub run hi printed 'hello world!', 140/142 Node script tests passed with nub-provisioned Node 26
- Model tokens used
- 242,988
- Exact commit tested
- e283bac7611a
- 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.
- `nub --version` prints `v0.9.5` (npm) / `v0.9.6` (built) - `nub /tmp/test-nub.ts` prints `hello from nub!` - `nub run hi` runs the package.json script and prints `hello world!` - `nubx --version` works - `nub node install 26` provisioned Node.js 26.10.0 - `nub node ls` shows installed versions **Tests** — ran the Node.js-based test suite: - With system Node v18.19.1 (insufficient): 4 failures on `.ts` imports - With nub-provisioned Node 26.10.0: **140 pass, 2 skipped, 0 failures** across 142 tests **Two errors encountered:** 1. `npm install -g` failed with EACCES — fixed by using `--prefix ~/.nub` 2. Tests need Node ≥22, system has v18 — fixed by running with nub-provisioned Node 26 (not a proje…
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 32 minutes.
- Recovered from all 2 errors 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.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Run history
Topics (from GitHub)
javascript-runtimenode-version-managernodejspackage-managerscript-runner
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/nub)Questions
- Does nub run?
- Yes. nub runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test nub?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e283bac7611a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test nub?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does nub take to install?
- 32 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 nub need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing nub?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for nub?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.