jquery
jQuery JavaScript Library
Runssource: GitHubhomepageJavaScriptMITcommit dc2b78f92c0e
JavaScript, MIT licensed. The project labels itself: jquery.
jquery runs. An Argusic agent installed it in 5 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
jQuery 4.0.0 builds successfully (all dist variants), passes all jsdom tests (14 passed, 1 expected skip), passes all 872 promises-aplus tests, all 20 node smoke tests, and 3 bundler smoke tests when using Node 22.12.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 emitted EBADENGINE warnings for packages requiring node >=20 while running node 181 minute
- npm run build failed: yargs-parser requires node >=201 minute
- jtr runner crashed on node 18 because html-encoding-sniffer require()s ESM module @exodus/bytes1 minute
- babel:tests failed on node 18 due to JSON import syntax in @babel/traverse0.5 minutes
- jsonlint fails on node 22 with invalid arg type for Glob0.5 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- npm run test:browserless exited 0: 3 bundler smoke tests passed, 20 node smoke tests passed, 872+872 promises-aplus tests passed, 14/15 jsdom QUnit tests passed (1 skipped as expected)
- Model tokens used
- 80,580
- Exact commit tested
- dc2b78f92c0e
- 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.
The repository is jQuery 4.0.0. The container came with Node v18.19.1, which is too old for many of… 1. **`npm install`** — succeeded with EBADENGINE warnings but installed 752 packages. 2. **`npm run build`** — failed because `yargs-parser` requires Node >=20. 3. **`npm run build:all`** — succeeded by setting `YARGS_MIN_NODE_VERSION=12`. 4. **`npm run pretest`** — `babel:tests` failed on Node 18 (JSON import syntax unsupported). `jtr` … **Fix**: Downloaded a Node v22.12.0 prebuilt binary to `/tmp/node-v22.12.0-linux-x64/` and ran ever… With Node 22, **`npm run test:browserless`** passed completely: - 3 bundler smoke tests (Rollup pure ESM, Rollup ESM+CJS, Webpack) - 20 node smoke tests (regular & factory, CJS/module/dual, all jquery variants) - 872+872 promises-aplus tests (both `deferred.cjs` and `when.cjs` adapters) - 14 passed / 1 skipped on jsdom QUnit (the skip is expected — "offset" test not supported on JSDOM) Also verified: `npm run build:all` produces all 12 expected dist files, and `npm run lint:dev` (esl…
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 5 minutes.
- Recovered from all 5 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.
- Measured 2 times, so the result is not a one-off.
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 5 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/jquery)Questions
- Does jquery run?
- Yes. jquery runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test jquery?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dc2b78f92c0e. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test jquery?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does jquery take to install?
- 5 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 jquery need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing jquery?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for jquery?
- 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.