pdfcraft

An open-source, clean-room reimplementation of Adobe Acrobat built in pure Rust

Could not verifysource: GitHubhomepageRustApache-2.0commit a6bc63a49795

Rust, Apache-2.0 licensed. The project labels itself: acrobat, acrobat full, acrobat pro, adobe, adobe acrobat, document processing, documents and pdf.

Argusic could not get pdfcraft running. An Argusic agent hit no errors on a clean machine with no GPU, and the whole session was recorded.

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 20 of 100 (the mean of this project's run scores).

At a glance

verdict
Could not verify
Argusic Score
20 / 100
cost of the verifying run
$0.21 (measured)
recorded runs
2
last tested
stars
5,146
forks
1,789
open issues
197
watchers
22
size
22 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.

Cold machine to finish
67 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
Exact commit tested
a6bc63a49795
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.

Install time
the run did not report one
How the result was proved
runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Model tokens used
not recorded for this run
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
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

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

/bin/sh -lc 'export PATH="$HOME/.cargo/bin:$PATH" && cd /work/repo && cargo test --workspace --no-f…
2026-10-09T09:52:34.735241Z ERROR codex_rollout::recorder: rollout writer failed for /home/runner/.…
2026-10-09T09:52:34.749572Z ERROR codex_core::session: failed to record rollout items: thread-store…
 succeeded in 649745ms:
   Compiling toml v1.1.6+spec-1.1.0
   Compiling calloop-wayland-source v0.4.1
   Compiling accesskit_atspi_common v0.18.1
   Compiling atspi v0.29.0
   Compiling wgpu-core-deps-windows-linux-android v30.0.1
   Compiling wayland-protocols-experimental v20250721.0.1
   Compiling wayland-protocols-misc v0.3.12
   Compiling glutin v0.32.3

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

  • Nothing broke on the way: zero errors between clone and running.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • An agent with no time limit did not get it running.

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.

  • docling verified to run · Python · 2 shared topics
  • takumi verified to run · Rust · 2 shared topics
  • PyPDFForm verified to run · Python · 2 shared topics

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Did not run20.000.21
Argusic Runner1/3Did not run20.000.22

Topics (from GitHub)

acrobatacrobat-fullacrobat-proadobeadobe-acrobatdocument-processingdocumentspdfpdf-generationpdf-processingpdf-toolspdf-viewerrust

Embed the badge

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

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

Questions

Does pdfcraft run?
Argusic could not verify that pdfcraft runs. Argusic installed and launched it on a clean machine, hitting 0 errors on the way, and recorded the session.
How did Argusic test pdfcraft?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a6bc63a49795. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test pdfcraft?
The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
Does pdfcraft need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pdfcraft?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for pdfcraft?
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