Skip to content

0.3.14: improved curved QR recovery

Latest

Choose a tag to compare

@TheCryptoDonkey TheCryptoDonkey released this 17 Nov 10:03
dd88998

QR 0.3.14 recovers more curved codes with a bounded quadratic fit to alignment measurements. Earlier successful reads keep priority, and format, version and payload validation remain strict. The recovery is available in TypeScript, optional WASM, Rust and Kotlin.

Accuracy scope 0.3.13 0.3.14 ZXing-WASM 3.1.7
Combined synthetic curved images 718/1,376 861/1,376 646/1,376
Separately frozen 256-image subset 65/256 118/256 77/256
Original photographs 180/184 180/184 171/184
Curved sheets 10/18 12/18 —

That is 143 additional exact reads in the curved comparison, with all earlier successful results preserved and no wrong QR payloads observed. All 64 negative controls remain rejected. ZXing still reads 14 curved frames QR misses; these dataset results are not a universal accuracy claim.

The twelve sampled new recoveries increase WASM median latency by 0.18–4.27% and TypeScript by 0.66–6.06% on the M4. The packaged WASM is 261,831 bytes, up 8,908 bytes. QR remains faster on the fixed clean/blank frames; random-noise rejection remains about 2.6× slower than ZXing.

Validated across the three ports, packaged TS/WASM parity, browser/worker/session use, 2,944 related photo views and repeated memory use. The specification, install examples and AI-readable documentation are updated.

Benchmark inputs, raw results and limits · Documentation · Choosing QR

Published and publicly verified on npm, JSR, crates.io and Maven Central. Documentation, docs.rs, jsDelivr and unpkg copies were also verified.

Release verification receipt records the exact source revision, seven successful CI/release workflows and six public readback receipts. npm provenance and installed API, JSR native Deno/npm compatibility, signed Maven artefacts and an independent consumer, crate checksums/source, and public documentation/CDN bytes all passed.