json

JSON for Modern C++

Runssource: GitHubhomepageC++MITcommit 21a69230bdaa

C++, MIT licensed. The project labels itself: bson, cbor, header only, json, json diff, json merge patch, json parser and json patch.

json runs. An Argusic agent installed it in 15 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

The JSON for Modern C++ library builds from source and all 124 unit tests pass on Ubuntu 24.04 with GCC 13.3.0.

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.04 (measured)
recorded runs
2
last tested
stars
50,936
forks
7,545
open issues
36
watchers
731
size
319 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.

Install time
15 minutes
Cold machine to finish
16 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
cmake .. -DJSON_BuildTests=On && cmake --build . -j$(nproc) && ctest -LE 'git_required|not_reproducible' returned 124/124 tests passed, 0 failed
Model tokens used
79,077
Exact commit tested
21a69230bdaa
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

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

[ 98%] Built target test-regression1_cpp11
[100%] Linking CXX executable test-msgpack_cpp11
[100%] Built target test-msgpack_cpp11
Everything worked perfectly on the first try — no errors to diagnose. The build succeeded, and all …
I'll now run the elapsed time measurement properly
exec
/bin/sh -lc 'start=$(stat -c%Z /work/repo/build/CMakeCache.txt 2>/dev/null || echo 0); now=$(date +…
 succeeded in 0ms:
Elapsed roughly 15 minutes
2026-11-01T13:32:54.053874Z ERROR codex_core::session: failed to record rollout items: thread 01a19…
tokens used
79,077

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 15 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, 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.
  • Following its own README: the documented path worked with nothing to fix.

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/3Runs100.000.04
Argusic Runner1/3Runs100.000.13

Topics (from GitHub)

bsoncborheader-onlyjsonjson-diffjson-merge-patchjson-parserjson-patchjson-pointerjson-serializationmessagepackmsgpackrfc-6901rfc-6902rfc-7049rfc-7159rfc-8259stl-containersubjson

Embed the badge

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

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

Questions

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