Yes. jira.js runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 0 errors on the way, and recorded the session.

How did Argusic test jira.js?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 392900765d4e. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test jira.js?

The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does jira.js take to install?

8 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 jira.js need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing jira.js?

Nothing did, in the recorded run: zero errors between clone and running.

Where is the evidence for jira.js?

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.

jira.js

Type-safe Jira REST API client for JavaScript and TypeScript. Supports Jira Cloud, Data Center, Agile, Service Management, Assets, Teams and organization APIs. Runtime response validation, tree-shakable ESM, Node.js and browsers.

Runssource: GitHub homepageTypeScriptMITcommit 392900765d4e

TypeScript, MIT licensed. The project labels itself: api client, atlassian, atlassian api, esm, javascript, jira, jira api and jira assets.

jira.js runs. An Argusic agent installed it in 8 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Node 22.23.4 plus pnpm 12.6.0 installed in the repo environment, dependencies installed, dist builds, all 408 unit tests pass, and the built library successfully fetched projects, issues, labels, and created an issue against a local schema-correct Jira mock while correctly reporting 401/404 errors.
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 90 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 90 / 100
cost of the verifying run: $0.05 (measured)
recorded runs: 2
last tested: 2026-11-08
stars: 492
forks: 60
open issues: 0
watchers: 3
size: 7 MB
created: 2020-01-02
last push: 2026-11-05

Subject data from GitHub, linked at the top of this page, refreshed 2026-11-08. 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.

Install time: 8 minutes
Cold machine to finish: 5 minutes
Errors hit and fixed: 0 hit, 0 fixed with no human help
How the result was proved: pnpm test exited 0, 34 files / 408 passed; mock-driven consumer against dist: project fetch printed 'PROJECT: MCP - Mock Project', issue fetch 'ISSUE: MCP-42 | summary: Mock issue summary', create printed 'CREATED: MCP-40800', labels 'LABELS: alpha,beta', 404 raised NotFoundError with isNotFoundError=true; pnpm build, typecheck, lint, check:browser, check:consumers all exited 0.
Model tokens used: 205,555
Exact commit tested: 392900765d4e
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.

205,555
All work is complete and verified. Final report:
**What I did**
- Read `README.md` and `CONTRIBUTING.md`: this is `jira.js` v6.4.0, a TypeScript Jira REST API clie…
- Initial gap: container had Node 18.19.1 and no `pnpm`. I downloaded the official prebuilt Node 22…
- Ran the standard install: `pnpm install` → exited 0, installed `zod 4.6.5` plus all devDependenci…
- Ran `pnpm build` → `tsc` + `tsc-alias` + Vite browser bundle all completed (`dist/browser.js` 882…
- Ran `pnpm test` → 34 test files, 408 tests, all passed (exit 0).
- Ran `pnpm typecheck` → sources, tests, and scripts all type-check clean.
- Ran `pnpm lint` → clean. Ran `pnpm check:browser` → `✔ browser-safe: 3630 runtime files clean, 36…
- Ran `pnpm check:consumers` → `[consumers] the packed tarball installs, imports and type-checks fr…
- No third-party keys were required for the above. To prove real behavior end to end, I stood up a …

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.
Nothing broke on the way: zero errors between clone and running.
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 did not, or is not known

Took 8 minutes to install, slower than the median of the 38 comparable projects Argusic has measured.

Of the 39 api-client projects Argusic has installed and timed, jira.js was the 24th fastest to reach a running state, and 24 of 39 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 8 minutes after the clone.
Following its own README: the documented path worked with nothing to fix.

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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.05	2026-11-08 07:27 UTC
Argusic Runner	1/3	Unverified	80.00	0.10	2026-11-08 07:22 UTC

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/jira.js.svg)](https://argusic.com/subject/jira-js)

Questions

Does jira.js run?: Yes. jira.js runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test jira.js?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 392900765d4e. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test jira.js?: The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does jira.js take to install?: 8 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 jira.js need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing jira.js?: Nothing did, in the recorded run: zero errors between clone and running.
How does jira.js compare with the alternatives?: Of the 39 api-client projects Argusic has installed and timed, jira.js was the 24th fastest to reach a running state, and 24 of 39 reached one at all.
Where is the evidence for jira.js?: 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.