Skip to content

Scanly SDK v2.0.0

Latest

Choose a tag to compare

@Yangjunjie-Lin Yangjunjie-Lin released this 18 Aug 02:03
· 22 commits to main since this release
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.