Skip to content

Releases: Yangjunjie-Lin/Scanly

Scanly SDK v2.0.0

Choose a tag to compare

@Yangjunjie-Lin Yangjunjie-Lin released this 18 Aug 02:03
v2.0.0
fea63b1

Scanly SDK v2.0.0 Stable

Scanly SDK v2.0.0 is the published Stable, privacy-first barcode scanning SDK for Web, Node.js, React, iOS, and Android. Decode, parsing, tracking, and industrial recovery run locally; the SDK has no image-upload, analytics, account, or cloud-decoder service.

Supported formats

QR Code Model 2, Data Matrix ECC 200, PDF417, Code 128, EAN-13, EAN-8, UPC-A, and UPC-E. The default remains QR-only for compatibility; select additional formats explicitly. DPM recovery is experimental and is not an industrial certification.

Published packages

npm latest points to 2.0.0 with provenance for:

  • @scanly/parsers
  • @scanly/scenario-schema
  • @scanly/benchmark
  • @scanly/core
  • @scanly/engine-jsqr
  • @scanly/engine-zxing-js
  • @scanly/engine-zxing-cpp-wasm
  • @scanly/browser
  • @scanly/node
  • @scanly/react

Native distribution

  • iOS 13+: ScanlySDK Swift Package Manager source package under native/ios in the immutable v2.0.0 tag. The repository root has no Package.swift, so v2.0.0 uses exact-tag checkout plus the local subdirectory package path. CocoaPods is not published.
  • Android API 24+: scanly-sdk-2.0.0.aar attached to this Release for arm64-v8a and x86_64. armeabi-v7a is unsupported. Maven Central is not published for v2.0.0.

Capabilities and integrity

The Stable API includes upload and realtime scanning, multi-code results, tracking, batch identity, bounded industrial recovery, Browser Worker execution, ZXing-C++ WASM, and Native wrappers. Qualification artifacts, checksums, SBOM, licenses, signing, API/ABI, and reproducibility records are attached or preserved under release/stable/.

See the MIT License, Third-Party Notices, and attached SBOM.

Physical qualification boundary

Physical Web iOS/Android, Native iOS/Android, 30-minute and 60-minute camera soaks, and the full device matrix remain POST_RELEASE_VALIDATION_PENDING under Issue #13. Automated browser, simulator, and emulator coverage is not physical-device qualification. No all-device-verified, device-certified, or industrial-certified claim is made.

Published artifacts and the v2.0.0 tag remain immutable.

Scanly v1.3.0 — Stable Maintenance Release

Choose a tag to compare

@github-actions github-actions released this 15 Jul 03:46
dbacd02

Scanly v1.3.0 — Stable Maintenance Release

Scanly v1.3.0 marks the first formal GitHub release of the current stable, feature-complete browser QR scanner.

Highlights

  • Privacy-first local processing with no image upload backend, storage, analytics, or tracking.
  • Dedicated Web Worker upload pipeline with transferable pixel buffers, real cancellation, stale-job protection, and recoverable Worker errors.
  • Layered decoding across region candidates, multi-scale crops, preprocessing, rotations, jsQR, and ZXing fallback.
  • Multiple-code completeness contracts instead of treating the first decoded payload as complete success.
  • Cross-browser Chromium, Firefox, and WebKit upload smoke coverage with automated accessibility checks.
  • Benchmark success-rate and performance regression gates, coverage gates, production builds, and CI artifact verification.
  • Upload safety limits, HTTP/HTTPS-only link actions, security headers, issue templates, Dependabot, and documented maintenance policy.

Verified project benchmark

  • Internal regression fixtures: 52
  • Successful fixtures: 51/52 (98.1%)
  • Retained known failure: 14-damaged

This benchmark is an internal regression suite, not a claim of universal QR-decoding accuracy or a third-party product comparison.

Compatibility

  • Node.js 20–24
  • npm 10+
  • Chrome / Edge: camera and upload supported
  • Firefox: upload supported; camera depends on browser and device permissions
  • Safari / iOS Safari: upload and camera supported under HTTPS and platform permission constraints

Project status

Stable · feature-complete · production deployed · maintenance mode.

Future work is limited to security, browser/API compatibility, dependency support, reproducible decoding improvements, and real bug reports.

Links