Skip to content

Latest commit

History

History
34 lines (24 loc) 路 1.81 KB

File metadata and controls

34 lines (24 loc) 路 1.81 KB

PQC Readiness Tracking Template

The Working Group has not settled on the final format, this version is an early draft intended to solicit input.

These pages track the state of Post-Quantum Cryptography (PQC) readiness for common libraries, software and hardware. This is a crowdsourced effort; please contribute by adding details about items you maintain or have reliable knowledge of.

Library Status Registry

Library Name Version Status Supported Algorithms Notes / Trackers
[Example Library] 1.0 馃敶 Not Supported ML-KEM, ML-DSA, ... Link to issue/PR

Status: 馃煝 Ready / 馃煛 In Progress / 馃敶 Not Supported

  • N.B. if you are forking this page for a new use case, update the heading before the table and first column name in the table to reflect the use case.

Readiness Criteria

  • Inventory: Does the package identify all non-PQC cryptographic dependencies?
  • Algorithm Support: Does it support NIST-standardized PQC algorithms?
  • Agility: Can the package switch between classical, hybrid, and PQC-only modes?

Status Definitions

  • 馃煝 Ready: at least 1 NIST-standardized key exchange algorithm (e.g. ML-KEM) AND at least 1 NIST-standardized signature algorithm (e.g. ML-DSA) are supported.
  • 馃煛 In Progress: only one of the two (key exchange OR signature) is supported, or support is in development/unreleased.
  • 馃敶 Not Supported: neither is supported.

How to Contribute

  1. Fork this repo.
  2. Update the table above with new information or edits.
  3. Submit a Pull Request with the tag [PQC-Readiness].

Guidance

  • All linked information should point to an official repository or technical documentation. If you provide a link to a press releases or product page, you will be asked to provide a different link.