Repository navigation
v0.3.12
Recover eleven more curved QR images by reading a strict header hypothesis from an already sampled refinement grid. Earlier successful results keep priority; version, Reed–Solomon and segment validation remain unchanged.
Across eight evaluated curved-image sets, QR 0.3.12 reads 571/992 against 500/992 for ZXing-WASM 3.1.7. The new 128-image set was frozen before evaluation and is now regression data. These finite results do not establish universal superiority. Photograph accuracy remains 180/184; all 64 negative controls are rejected.
TypeScript, Rust and Kotlin implement the same bounded recovery. The change adds no image sampling, maps or second looks. It may retain one additional grid and perform one additional strict symbol validation after all earlier paths fail.
Across two paired M4 runs, the five measured new reads change WASM median latency by -0.34–0.32% relative to their earlier misses. The three cases with a selected header that still fails to decode change by -0.58–0.01%; earlier successful curved cases change by -0.88–1.46%. These measurements do not establish a general speed improvement or a worst-case bound.
Install from npm (@forgesworn/qr), JSR (@forgesworn/qr), crates.io (forgesworn-qr) or Maven Central (io.github.forgesworn:qr) at version 0.3.12. All four registries are published and verified, including installed npm, native Deno, npm compatibility and independent Gradle consumers. Documentation and CDN files match the release, and the crate archive checksum and sources are verified. See the attached release verification receipt and its six linked public readbacks.
See choosing QR for fit and limitations and performance evidence for exact sources, inputs and measurements.