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.

StatusMeaning
ReadyPQC is supported in a stable release and enabled by default where it applies (for example, hybrid key exchange on by default).
AvailablePQC is supported in a stable release, but you have to opt in.
PartialOnly some algorithms are supported (for example, KEM but not signatures), or support is experimental or behind flags.
PlannedNot supported yet, but there is a public plan.
No planNo support and no public plan found.
UnknownNot researched yet, or the evidence is inconclusive.
DelegatesThe 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

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

How data is collected

  1. 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.
  2. A language model drafts a status proposal from that material, citing a quote for every field.
  3. 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.
  4. 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.