Scoreboard

Real output, updated as the port moves. Nothing here is a target.

Original suite

BinaryPassedFailedNotes
tst_encoder1,5960
tst_parser2,5060
tst_tojson8270
tst_c9010header compiles under -std=c90 -pedantic
tst_cppn/an/ainapplicable, see decision 2
Total4,9290of 4,929 reachable

Everything that can pass, passes, and nothing is stubbed any more. The last one was _cbor_value_dup_string, which no row in the suite reaches. It has its own differential test under tests/port/ instead, run by make test against upstream's own archive.

ABI

CheckResult
Exported symbols44 / 44
nm diff vs upstreamempty
Struct sizes and offsetsasserted, passing
C90 header cleanlinesspassing

Budget

Parse speed vs C0.37x, faster on all 8 files (2.7x)
Pretty-print vs C0.23x (4.4x), but see methodology
unsafe blocks80 (all in cbor-ffi)
Third-party dependencies0
Differential fuzz13.5M execs, zero divergences, four targets, history
Tools vs upstreamexact on 4,509 documents x 20 flag combinations, decision 18
Decision log entries25

Reading this honestly

4,929/4,929 is every row that can apply to a port. It is not 4,931 because two rows test that upstream's C compiles as C++, which a Rust port cannot satisfy by construction.

The speed numbers under it need reading carefully in the other direction. Parsing is faster than the C on all eight corpus files now, but it was 1.49x slower on all eight for a day, and the history table in the methodology keeps that figure rather than erasing it. The print number is 4.4x and most of it is upstream's vfprintf per byte, not decoding, which the methodology says before it quotes it.

If the port ends below 100%, the failing tests stay failing and each gets a paragraph in the decision log. A reproducible 94% is worth more than a 100% that required editing the suite.


Two of those rows need a footnote about what make test actually runs. The 4,509 documents were the accumulated fuzz corpus, which is generated and not committed, so a fresh clone checks the nine documents that are: 180 cases plus a 16-document round trip. Point the harness at your own corpus to repeat the wide sweep:

$ tests/port/tools_diff.sh fuzz/corpus/pretty_diff/*

The fuzz total is the same shape of claim, answered by the ledger. Comparing the tools also needs upstream's cbordump and json2cbor binaries, which are not vendored the way the archive is; without them make test-tools says so and skips, and the 4,929 rows above are unaffected. Every other target here, make fuzz and make bench included, runs from a fresh clone.


Verified 2026-08-02. Reproduce with make test, make symbols, make lint, python3 bench/run.py.