kitsu
🦊 A simple, lightweight & framework agnostic JSON:API client
Runssource: GitHubhomepageTypeScriptMITcommit 1ab8739506fe
TypeScript, MIT licensed. The project labels itself: api client, async, async await, ecmascript, esm, hacktoberfest, javascript and json api.
kitsu runs. An Argusic agent installed it in 2.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Full test pipeline passes on Node 22; all 382 tests pass, CJS and ESM imports work, size limits respected, and a mock JSON:API server round-trip confirmed Kitsu fetches and deserialises correctly
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.
- yarn lockfile resolves [email protected] which requires Node 20+ but only Node 18 available1 minute
- Built CJS output named .js in "type":"module" package; require('kitsu') fails per README promise0.8 minutes
- Build failure: import attribute 'with { type: 'json' }' syntax unsupported by Node 180.7 minutes
- docs:typescript fails with TS5112 on TypeScript 6.0.3 (flags changed)0.5 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- yarn test exited 0 (38 suites, 382 tests, 100% coverage, lint, docs lint, build, size-limit all green); require('./dist/index.cjs') returns Kitsu class; import('./dist/index.mjs') returns Kitsu class; mock server GET /anime fetched and deserialised JSON:API response correctly
- Model tokens used
- 271,740
- Exact commit tested
- 1ab8739506fe
- 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.
M packages/kitsu/package.json M packages/kitsu/rollup.config.mjs ---DIFF STATS--- packages/kitsu-core/package.json | 138 +++++++++++++++++----------------- packages/kitsu-core/rollup.config.mjs | 2 +- packages/kitsu/package.json | 18 ++--- packages/kitsu/rollup.config.mjs | 2 +- 4 files changed, 80 insertions(+), 80 deletions(-) Everything works end-to-end. Here's the final report: tokens used 271,740 Everything works end-to-end. Here's the final report:
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.5 minutes, faster than the median of the 39 comparable projects Argusic has measured.
- Recovered from all 4 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.
Of the 40 api-client projects Argusic has installed and timed, kitsu was the 14th fastest to reach a running state, and 25 of 40 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.5 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)
api-clientasyncasync-awaitecmascriptesmhacktoberfestjavascriptjson-apijson-api-serializerkitsukitsu-apikitsu-ionodejsnpmpromise
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kitsu)Questions
- Does kitsu run?
- Yes. kitsu runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test kitsu?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1ab8739506fe. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test kitsu?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kitsu take to install?
- 2.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 kitsu need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kitsu?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does kitsu compare with the alternatives?
- Of the 40 api-client projects Argusic has installed and timed, kitsu was the 14th fastest to reach a running state, and 25 of 40 reached one at all.
- Where is the evidence for kitsu?
- 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.