Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributeoqs

Dart FFI bindings for liboqs enabling post-quantum cryptography primitives like ML-KEM and ML-DSA.

pub.devRemove
webcrypto

Cross-platform implementation of Web Cryptography APIs for Dart.

pub.devRemove
ScoresHealth6189 (best)
Maintenance8698 (best)
Quality94 (best)91
Popularity1072 (best)
Community680 (best)
Compatibility93100 (best)
UsageDownloads (30 days)43657k (best)
Likes984 (best)
Pub points160 / 160 (best)140 / 160
GitHub stars7115 (best)
MaintenanceLatest release4.2.0, 4 weeks ago0.6.2, 10 days ago (best)
Major versions in 12 months20 (best)
Contributors139 (best)
PublisherUnverifiedgoogle.dev
FitPlatformsAndroid, iOS, Windows, macOS, LinuxAndroid, iOS, Web, Windows, macOS, Linux
WASM-readyNoYes
KindFFI (native library)FFI (native library)
Code generationNoNo
Direct dependencies1 (best)5
LicenseMITAPACHE-2.0
Setup effortHighMedium
JudgementStrengths
  • High-performance post-quantum cryptography support via native liboqs bindings.
  • Cross-platform support covering Android, iOS, Windows, macOS, and Linux.
  • Includes constant-time comparison methods to guard against timing side-channels.
  • Consistent API across mobile, web, and desktop platforms.
  • Backed by BoringSSL natively and window.crypto on the web.
  • Extensive feature set including AES, RSA, ECDSA, HMAC, and hashing algorithms.
Weaknesses
  • Requires manual setup and management of native liboqs binaries for each target platform.
  • Changes upstream in liboqs (such as breaking name changes or removed algorithms) directly impact the Dart API behavior.
  • Requires cmake and a C compiler (like gcc or clang) for native builds.
  • Native implementation executes on the main thread.
  • Some browser and platform specific compatibility limitations and known issues.
WarningsNoneNone
oqs vs webcrypto: which Flutter package should you use? | pubscout