Guides
Practical notes on finding the encryption in your code and moving it to quantum-safe methods.
- The Hard Keel quantum readiness score
An open, versioned way to grade a code repository's readiness for post-quantum encryption, from A+ to F, aligned with NIST's 2030 and 2035 dates. How it is computed, and how to put the badge on your README.
- We scanned 100 popular open-source projects for encryption quantum computers will break
About a third use RSA or elliptic-curve encryption directly in their own code. Seven have started on post-quantum. Most MD5 and SHA-1 turned out to be harmless. Results from 100 of GitHub's most-starred projects.
- NIST's final post-quantum timeline: what changes for your code
NIST IR 8547 is final. Every strength of RSA and elliptic-curve encryption is deprecated after 2030 and disallowed after 2035. Here is what that means for application teams, and what to do first.
- How to find quantum-vulnerable encryption in your code
Where RSA and elliptic-curve encryption hide in a codebase, the search patterns for Python, JavaScript, Go and Java, and how to turn the results into an inventory you can plan from.
- Replacing MD5, SHA-1, DES, ECB and RSA-1024: what to use instead
Weak encryption that still turns up in code, why each one is a problem, and the replacement with code examples for Python, JavaScript, Go and Java.