CipherChecker · Post-Quantum Readiness

The data you encrypt today
can be harvested now, decrypted later.

A quantum computer that breaks today's public-key crypto doesn't exist yet — but adversaries are recording encrypted traffic now to crack once it does. Point CipherChecker at a public GitHub repo and it scans the real dependency manifests, flags the cryptography a quantum computer will break, and names the exact NIST replacement.

Try a real one: · ·
Reads package.json, requirements.txt, go.mod, Cargo.toml, pom.xml, Gemfile, composer.json from the repo's default branch. Presence of a library is a signal to review — not proof of vulnerable use. Prefer manifests? Paste them directly →

Quantum readiness

Why "later" still matters today

Today — traffic captured
Stored, waiting
Quantum decrypt

Anything with a multi-year confidentiality lifetime — health records, legal files, state secrets, long-term contracts — is already exposed if it crosses a vulnerable channel today. The migration clock started before the computer arrived.

What this is

CipherChecker has two cleanly separated layers. The classifier core — the logic mapping each primitive to its quantum threat and its NIST-standardized replacement (ML-KEM / FIPS 203, ML-DSA / FIPS 204, SLH-DSA / FIPS 205) — is dependency-free and built to ship as open source. The hosted scan layer wraps it as a service that reads real repositories.

This page runs a real scan: it fetches the repository's actual manifests from GitHub and classifies the libraries it finds. Nothing here is canned. When a library is flagged it is flagged for review — its presence shows the codebase can use a quantum-vulnerable primitive, which is where migration work begins.