foliate-js

Render e-books in the browser

Runs with mockssource: GitHubhomepageJavaScriptMITcommit 78914aef4466

JavaScript, MIT licensed. The project labels itself: azw, azw3, cbz, cfi, dictd, ebook, ebook reader and epub.

foliate-js runs, with stand-ins for the services it depends on. An Argusic agent installed it in 14.8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

npm install complete, Rollup build produces vendor/ artifacts (fflate.js, zip.js, pdfjs/), epubcfi test suite passes 22/23 assertions via JSDOM runner (the single failure is a JSDOM CDATA limitation), and all 5 core modules (epub.js, paginator.js, overlayer.js, progress.js, view.js) import successfully with DOM polyfills

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 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.08 (measured)
recorded runs
2
last tested
stars
1,157
forks
302
open issues
74
watchers
10
size
7 MB
created
last push

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.

Time lost to each failure while testing foliate-js, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • JSDOM CDATA handling mismatch: CDATA sections become comment nodes, breaking isTextNode logic in page2 tests0.5 minutes
Install time
15 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
node run-tests.mjs: 22/23 assertions passed, 5 core modules imported successfully, npm run build exited 0
Model tokens used
100,736
Exact commit tested
78914aef4466
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
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

  final_state: 'npm install complete, Rollup build produces vendor/ artifacts (fflate.js, zip.js, p…
}));
\"" in /work/repo
 succeeded in 0ms:
{"install_succeeded":true,"launch_succeeded":true,"install_minutes":14.8,"errors":[{"msg":"JSDOM CD…
exec
/bin/sh -lc 'rm /work/repo/run-tests.mjs' in /work/repo
 succeeded in 0ms:
2026-10-10T11:15:57.138036Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
2026-10-10T11:15:57.138081Z ERROR codex_core::session: failed to record rollout items: thread 01a12…
tokens used
100,736

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

  • Installed in 14.8 minutes.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • 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

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.08
Argusic Runner1/3Did not run20.000.24

Topics (from GitHub)

azwazw3cbzcfidictdebookebook-readerepubepub-readerfb2mobiopdsreaderstardict

Embed the badge

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

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

Questions

Does foliate-js run?
foliate-js runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test foliate-js?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 78914aef4466. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test foliate-js?
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 foliate-js take to install?
14.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 foliate-js need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing foliate-js?
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.
Where is the evidence for foliate-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.

Discussion