FIPS 203 · 204 · 205 readiness

Are your dependencies ready for post-quantum crypto?

NIST standardised ML-KEM, ML-DSA and SLH-DSA in 2024. PQC Deps tracks which open-source libraries support them, since which version, and what's planned. Every claim links to its source.

Check my project →Paste a package.json, go.mod or requirements.txt. Parsed in your browser.

92 libraries, one square each, coloured by status. Browse the catalog

The catalog at a glance

10 of 92 are ready today, and 47 support post-quantum crypto in some form.

01

Evidence, not guesses

Every field cites release notes, docs, commits or maintainer posts, with a quote you can check. No source means unknown.

02

Follows the chain

A JWT library that calls the platform's crypto, or an HTTP client on top of OpenSSL: we show who actually does the cryptography.

03

Open data

Each library is a YAML file on GitHub, refreshed daily. Corrections are pull requests. Contribute.

Check my project

Paste a manifest. See what to upgrade.

The checker reads npm, PyPI, Go, Maven, Cargo and NuGet manifests and lockfiles, matches them against the catalog, and tells you which packages already support post-quantum crypto, from which version, and which delegate to something else.

Open the checker →