ML-DSA (FIPS 204)
For ML-DSA (FIPS 204), purpose is digital signature; current status is Approved; planned status is post-quantum standard, published August 2024; replacement is N/A (this is the replacement); source document is FIPS 204, recorded from its source on 2026-08-16; source re-checked 2026-11-18.
- Algorithm
- ML-DSA (FIPS 204)
- Purpose
- digital signature our reading
- Current status
- Approved our reading
- Planned status
- post-quantum standard, published August 2024 our reading
- Replacement
- N/A (this is the replacement) our reading
- Source document
- FIPS 204 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: ML-DSA (FIPS 204) — 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/ml-dsa-fips-204/, checked 2026-11-18.
What the source says
Module-Lattice-Based Digital Signature Standard (ML-DSA)
— csrc.nist.gov, retrieved 2026-08-16
Source
- csrc.nist.govhttps://csrc.nist.gov/projects/post-quantum-cryptography
Does your own code still call ML-DSA (FIPS 204)? 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