pdf.js

PDF Reader in JavaScript

Runssource: GitHubhomepageJavaScriptApache-2.0commit 638bcdf0ada7

JavaScript, Apache-2.0 licensed.

pdf.js runs. An Argusic agent installed it in 1.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.

PDF.js project installs and builds successfully with Node.js v22; the unit test suite passes all 3424 tests across Chrome and Firefox browser targets; the generic build produces functional pdf.mjs, pdf.worker.mjs, pdf.renderer.mjs, pdf.sandbox.mjs, and viewer.html artifacts.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.07 (measured)
recorded runs
2
last tested
stars
54,163
forks
10,739
open issues
466
watchers
1,086
size
223 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 pdf.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.

  • Node.js v18 installed but project requires >=22.22.32 minutes
  • Puppeteer Chrome browser missing/incomplete installation1 minute
  • No unzip utility for Puppeteer browser extraction0.5 minutes
  • Font tests fail - fonttools/ttx not available (system dependency)
Install time
2 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
npx gulp unittest exited 0: 'Run 3424 tests - All unit tests passed, runtime 71.7s'. npx gulp generic compiled successfully: all webpack bundles emitted. Built pdf.mjs loads in Node.js without errors.
Model tokens used
136,185
Exact commit tested
638bcdf0ada7
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.

npm version: 10.9.9
Build artifacts (build/generic/build/):
total 3.5M
-rw-rw-r-- 1 runner runner 862K Nov  1 13:30 pdf.mjs
-rw-rw-r-- 1 runner runner 257K Nov  1 13:30 pdf.renderer.mjs
-rw-rw-r-- 1 runner runner 116K Nov  1 13:30 pdf.sandbox.mjs
-rw-rw-r-- 1 runner runner 2.3M Nov  1 13:30 pdf.worker.mjs
Build artifacts (build/generic/web/viewer.html):
-rw-rw-r-- 1 runner runner 67K Nov  1 13:30 /work/repo/build/generic/web/viewer.html
Unit test summary: all 3424 tests passed
tokens used
136,185

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 1.5 minutes, faster than the median of the 14 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 Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 15 JavaScript projects Argusic has installed and timed, pdf.js was the 7th fastest to reach a running state, and 10 of 15 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 1.5 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.07
Argusic Runner1/3Runs100.000.04

Embed the badge

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

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

Questions

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