Repository navigation
QR 0.3.9: late refinement for curved maps
Recover curved maps that previously received ordinary refinement without the late alignment pass. One strict retry runs only after all earlier paths fail; existing successful results and metadata retain priority.
| Dataset | 0.3.8 | 0.3.9 | ZXing-WASM 3.1.7 |
|---|---|---|---|
| Earlier 128 distortions | 103 | 106 | 106 |
| Previous 128-image holdout | 62 | 63 | 52 |
| Earlier separate 128-image holdout | 71 | 72 | 67 |
| New frozen 128-image set | 79 | 80 | 70 |
| Curved sheets, 18 images | 6 | 9 | Not measured |
The 96-image distortion set stays at 48 correct reads against ZXing’s 42. No earlier successful result changes, and no wrong QR payload is observed in these finite datasets. This does not establish universal superiority over ZXing.
TypeScript, Rust, Kotlin and packaged WASM remain aligned. All 498 TypeScript tests and the 77-frame conformance pack pass; all 74 previous conformance entries remain unchanged. The packaged WASM is 237,214 bytes (+2,423 bytes). The maximum becomes seven refinement attempts, trading extra work on some difficult failures for accuracy. Newly recovered reads take 13–18% longer in WASM than the previous failed reads; routine WASM medians are essentially unchanged. TypeScript clean-frame p95 rises by 0.89–1.09 ms in the paired runs.
See performance results and limitations, reproduction evidence and the distribution guide.
Published and independently verified on npm, JSR, crates.io and Maven Central. Documentation and both CDN copies match the release bytes. All seven workflow runs passed; npm provenance, JSR native/compatibility consumers and signed Maven artefacts with a separate consumer were checked.
Release verification receipt links the six public readbacks.