HQC
For HQC, purpose is key establishment; current status is selected for ongoing standardization; planned status is standardization underway; replacement is N/A (this is a future post-quantum standard); source document is NIST PQC project, recorded from its source on 2026-08-16; source re-checked 2026-11-18.
- Algorithm
- HQC verified
- Purpose
- key establishment our reading
- Current status
- selected for ongoing standardization our reading
- Planned status
- standardization underway our reading
- Replacement
- N/A (this is a future post-quantum standard) our reading
- Source document
- NIST PQC project our reading
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
Cite as: HQC — NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when (NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when), referencesource.org/nist-cryptographic-algorithm-deprecation-schedule/hqc/, checked 2026-11-18.
What the source says
HQC key encapsulation mechanism were selected for ongoing standardization;
— csrc.nist.gov, retrieved 2026-08-16
Source
- csrc.nist.govhttps://csrc.nist.gov/projects/post-quantum-cryptography
Does your own code still call HQC? npx crypto-deprecation-check reads the places where naming an algorithm is the point of the line -- createHash, a JWT alg, Cipher.getInstance, MODE_ECB, generateKeyPair, createECDH, an SSH HostKeyAlgorithms setting, an openssl subcommand -- and prints the status we hold for each with this page's sentence quoted. It fails a build only on a status that is already deprecated or disallowed, says nothing at all about algorithms we hold no record for, and makes no network calls. crypto-deprecation-check on npm