json-machine
Efficient, easy-to-use, and fast PHP JSON stream parser
Runssource: GitHubPHPApache-2.0commit 03d006d29948
PHP, Apache-2.0 licensed. The project labels itself: json iterator, json parser, json stream, parsing, php and stream processing.
json-machine runs. An Argusic agent installed it in 5.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PHP 8.3.32 and Composer 2.11.2 installed via static binaries; composer install completed with 53 dependencies; all 841 PHPUnit tests pass (1856 assertions); json-machine library correctly parses JSON via Items::fromString().
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.
- PHP and Composer not pre-installed in container - no apt install permission4.5 minutes
- composer scripts call 'composer' directly but it's not in PATH0.5 minutes
- AutoloadingTest::testLoadsFilesInComposerJson fails because it runs 'php -r' via shell_exec and 'php' is not in PATH0.5 minutes
- Install time
- 6 minutes
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- phpunit exited 0 with 'OK (841 tests, 1856 assertions)' and manual Items::fromString() test printed correct parsed output
- Model tokens used
- 45,446
- Exact commit tested
- 03d006d29948
- 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.
ERRORS! exec /bin/sh -lc 'cd /work/repo && PATH="/home/runner/.local/bin:$PATH" /tmp/php vendor/bin/phpunit 2>&1… succeeded in 1301ms: Time: 1.12 seconds, Memory: 10.00 MB OK (841 tests, 1856 assertions) All 841 tests pass (1856 assertions) once `php` is in PATH. Now let me report the ARGUSIC_RESULT: tokens used 45,446 All 841 tests pass (1856 assertions) once `php` is in PATH. Now let me report the ARGUSIC_RESULT:
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 5.5 minutes.
- Recovered from all 3 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.
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 5.5 minutes after the clone.
Run history
Topics (from GitHub)
json-iteratorjson-parserjson-streamparsingphpstream-processing
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/json-machine)Questions
- Does json-machine run?
- Yes. json-machine runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test json-machine?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 03d006d29948. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test json-machine?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does json-machine take to install?
- 5.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 json-machine need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing json-machine?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for json-machine?
- 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.