Post-quantum cryptography, in plain language
A quantum computer big enough to break today's public-key cryptography doesn't exist yet — but the migration clock has already started, because encrypted data stolen today can be decrypted later. These guides explain what's at risk, why, and what to do about it. No PhD required.
What is "harvest now, decrypt later"?
Why data you encrypt today can be stolen now and read later.
Is RSA quantum-safe?
No — and here's exactly why, and what replaces it.
Is ECDSA quantum-safe?
No. The signature scheme behind TLS and most wallets.
Is X25519 quantum-safe?
Surprisingly, no — "modern" doesn't mean "post-quantum".
For compliance & security teams
NIST IR 8547, explained
The transition timeline: deprecate 2030, disallow 2035.
CNSA 2.0, explained
The quantum-safe suite and its deadlines.
What is a CBOM?
The cryptographic inventory auditors ask for first.
Want to know what's in your code?
Scan a repo →…or run it on every push in your own CI. The GitHub Action scans on your runner, so nothing leaves the box.