SaQura SDKs · Upgrade notes
Versions & compatibility
All SDKs
For every SaQura SDK you find here, before you update: which data the new version reads, whether your license file still verifies, what is optional, and whether R8 rules or trimming stay unchanged. All facts come from the published packages.
| SDK | Current version | Package | Notes |
|---|---|---|---|
| SaQura .NET | 1.0.15 | NuGet | Versions & compatibility |
| SaQura Kotlin | 1.2.1 | Maven Central | Versions & compatibility |
| SaQura Swift | 1.2.0 | saqura.de/swift | Versions & compatibility |
| SaQura JS / TS | 0.1.0 | npm | Versions & compatibility |
| SaQura Python | 1.0.9 | PyPI | Versions & compatibility |
| SaQura C / C++ | 1.0.0 | saqura.de/downloads | Versions & compatibility |
The same for every SDK
- The same license file (.lic) works with every SaQura SDK. Unbound licenses are not affected by app binding: no call changes, no re-issue needed.
- Data formats are byte-identical across all SDKs: what one SDK encrypts or signs, every other one decrypts and verifies. New algorithms are added; an existing format is not changed without the new version still reading the old one.
- Post-quantum algorithms per FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) are implemented in every SDK via liboqs 0.15.