Methodology
How we decide a library's status, where the evidence comes from, and how often it's checked.
Status definitions
Each library gets exactly one overall status.
| Status | Meaning |
|---|---|
| Ready | PQC is supported in a stable release and enabled by default where it applies (for example, hybrid key exchange on by default). |
| Available | PQC is supported in a stable release, but you have to opt in. |
| Partial | Only some algorithms are supported (for example, KEM but not signatures), or support is experimental or behind flags. |
| Planned | Not supported yet, but there is a public plan. |
| No plan | No support and no public plan found. |
| Unknown | Not researched yet, or the evidence is inconclusive. |
| Delegates | The library does not do asymmetric crypto itself; it delegates to another library. See that library. |
"Where it applies" matters. Each entry lists the algorithms that are relevant to it: a JWT library has no TLS key exchange, and a TLS library may not expose signatures. A library is ready when post-quantum protection is on by default for at least one applicable algorithm, in a stable release, without experimental flags.
Algorithms tracked
- ML-KEM (FIPS 203): key encapsulation
- ML-DSA (FIPS 204): signatures
- SLH-DSA (FIPS 205): hash-based signatures
- Hybrid TLS (e.g. X25519MLKEM768): tls key exchange
- FN-DSA (Upcoming standard): signatures. Tracked ahead of standardization.
- HQC (upcoming): key encapsulation. Tracked ahead of standardization.
For each algorithm we record whether it's supported (yes, partial, no or unknown), the first stable version, whether it's on by default or opt-in, and whether it's experimental.
Evidence rules
- Every claim cites a source: release notes, changelogs, documentation, commits, issues, pull requests or maintainer posts.
- Every source carries a verbatim quote, so you can find the exact sentence on the page.
- No source means unknown. We don't fill gaps from memory or assumptions.
- Each entry has a last verified date. Entries older than 90 days are flagged as possibly out of date.
How data is collected
- An automated pipeline fetches each library's recent releases, changelog, documentation and GitHub issues and pull requests that mention ML-KEM, Kyber, ML-DSA, Dilithium, SLH-DSA, X25519MLKEM768, post-quantum or PQC.
- A language model drafts a status proposal from that material, citing a quote for every field.
- The pipeline checks that each quote really appears in the fetched page. Any field whose quote can't be found is dropped back to unknown.
- The proposal is opened as a pull request. A human reviews every change before it's published. The pipeline can't publish on its own.
Update frequency
The pipeline re-runs weekly to catch new releases. Anyone can suggest a correction at any time through a GitHub issue or pull request.
Delegation
Many packages don't implement cryptography themselves: they call the platform's crypto, OpenSSL, or another library. We record this as a delegates to link and show the chain, so you can see which library actually needs to support post-quantum algorithms.
Limits
This is not a security audit. Support in a library doesn't mean your application uses it: you may still need to upgrade, configure or call new APIs. Always check the linked sources.