vendor · quantum risk
PQC libraries | Quantum-Safe Claims & Education
Verdict
PQC libraries enable migration but do not make your deployment quantum-proof until integrated, configured, and operated correctly. Track versions, constant-time quality, and hybrid APIs.
Overview
Open libraries (liboqs, OpenSSL providers, language bindings) are how most teams experiment with NIST PQC.
Educational pages summarize public roles—always verify current project docs for algorithms and support status.
Cryptographic profile
Claim scrutiny (buyer checklist)
Marketing / stated claims
- Production-ready PQC library
Open questions
- Support SLAs vs research releases?
Educational analysis only. Verify primary sources, specs, and audits yourself before any financial or procurement decision.
What breaks
- Stale library versions in production
- Custom forks without review
- Hybrid misconfiguration leaving classical-only paths
Mitigations
- Pin and monitor library CVEs and releases
- Prefer well-reviewed hybrids
- Test performance and size impacts early
FAQ
Which library should I use?
Depends on stack—evaluate OpenSSL integration, language, and support; this is not product advice.
Related standards?
/standards/ml-kem and ml-dsa
Key concepts (technical dictionary)
Terms used on this page — open a definition: