HARD KEEL
Hard Keel Quantum Scan

Find the encryption quantum computers will break, before 2030.

Quantum Scan checks your code and cloud setup for weak encryption, exposed settings and leaked passwords, then gives you a plan to fix them. Run it once from the command line, or have it check every code change on GitHub.

npx @hardkeel/quantum-scan
Free and open source. No account. Your code never leaves your machine. Or install on GitHub to check every pull request
What it checks

Five kinds of problem, in code and config.

  • Encryption quantum computers will break. RSA, elliptic curve (ECDSA, ECDH, Ed25519, X25519) and Diffie-Hellman.
  • Weak encryption. MD5, SHA-1, DES, 3DES, RC4, ECB mode, DSA, RSA keys under 2048 bits, TLS 1.0 and 1.1.
  • Weak TLS in server config. Old versions and weak cipher suites in nginx, Apache, HAProxy, load balancer and CDN settings.
  • Exposed settings. Public storage and databases, admin ports open to the whole internet, encryption at rest turned off, certificate checks turned off.
  • Leaked keys and passwords. Private keys, cloud and API tokens, passwords in connection strings. Masked in all output.

Reads Python, JavaScript, TypeScript, Go and Java, with community rules for Rust, C#, PHP, Ruby, Swift and C or C++, plus Terraform, CloudFormation, Kubernetes, Dockerfiles, nginx, Apache and HAProxy. To check your websites and the machine it runs on as well, use quantum-scan map. It asks before each one.

Sample

A real scan of a made-up shop.

We built Harbor Shop, a small demo codebase with the mistakes we see most often, and ran the free scanner on it. This is the output, unedited.

harbor-shop $ npx @hardkeel/quantum-scan --offline --quiet
Hard Keel Quantum Scan · 8 files scanned

Quantum readiness: F (0/100, Hard Keel method v1). A leaked key or password holds the grade at D or lower until it is revoked and removed.

Found 3 leaked keys or passwords, 6 uses of weak encryption, 6 exposed infrastructure settings and 2 uses of encryption quantum computers will break.

Fix now
  app/settings.py:2  AWS access key
    Revoke it and issue a new one, then load it from a secret store. Deleting it from the code leaves it in git history.
  app/settings.py:3  Database password in URL
    Revoke it and issue a new one, then load it from a secret store. Deleting it from the code leaves it in git history.
  deploy/tls.key:1  Private key
    Revoke it and issue a new one, then load it from a secret store. Deleting it from the code leaves it in git history.
  app/payments.py:6  RSA-1024 key
    Use 3072-bit keys or larger now, then plan the move to post-quantum methods.
  app/payments.py:10  ECB mode
    Switch to AES-256-GCM.
  deploy/nginx.conf:4  TLS 1.0/1.1
    Require TLS 1.2 or later, ideally TLS 1.3.
  deploy/nginx.conf:5  Weak TLS ciphers
    Allow only AES-GCM and ChaCha20 cipher suites.
  gateway/server.go:11  TLS 1.0/1.1
    Require TLS 1.2 or later, ideally TLS 1.3.
  infra/main.tf:7  Public storage
    Block public access. Share files through signed links or a CDN with access control.
  infra/main.tf:8  Public storage
    Block public access. Share files through signed links or a CDN with access control.
  infra/main.tf:9  Public storage
    Block public access. Share files through signed links or a CDN with access control.
  infra/main.tf:10  Public storage
    Block public access. Share files through signed links or a CDN with access control.
  infra/main.tf:20  SSH (22) open to the whole internet
    Limit the source to known addresses or a VPN, or put it behind a private network.
  infra/main.tf:28  Encryption at rest off
    Turn on encryption at rest, ideally with a customer-managed key.
  app/payments.py:15  MD5 hash
    Switch to SHA-256 or SHA-3, unless it is only a non-security checksum.

Plan for later
  Safe today, but quantum computers will be able to break these. NIST plans to phase them out between 2030 and 2035.
  api/auth.ts:4  ECDH key exchange
    Move key exchange to ML-KEM (FIPS 203), or hybrid X25519 + ML-KEM-768 for TLS.
  api/auth.ts:8  ECDSA signature
    Move to ML-DSA (FIPS 204) or SLH-DSA (FIPS 205) signatures.

Every key and password in Harbor Shop is fake, planted for the demo.

On GitHub

The same checks on every pull request, kept up to date without anyone asking.

01

Checks every pull request

Flags leaked keys, weak encryption such as MD5, DES, short RSA keys or old TLS, exposed settings such as public storage or open admin ports, and encryption quantum computers will break. Only the last is a heads-up instead of a failed check.

02

Keeps an encryption inventory

Lists every use of encryption in the repository, by algorithm and file. Exports as a CycloneDX cryptographic bill of materials for auditors and security teams.

03

Plans the migration

Puts the work in order against NIST's timeline, key exchange first, and names the quantum-safe replacement for each item.

Beyond the code

Encryption is one layer.

Most breaches start with a person: a phished password, a shared admin account, a step skipped because nobody wrote it down. Keep tools that touch production sandboxed, give each account only the access it needs, teach people to spot social engineering, and write down the procedures your team follows.

For data in the cloud, use end-to-end encryption, so the provider only ever holds data it can't decrypt.

Why now

Data encrypted today can be recorded and read later.

RSA and elliptic-curve encryption protect almost everything sent over the internet. A large enough quantum computer will break both. NIST's final transition plan, published in October 2026, deprecates them after 2030 and disallows them after 2035, and attackers can store traffic now to decrypt once that day comes.

Most teams don't know where their encryption lives. That inventory is the first step, and it's the one Quantum Scan keeps current.

  • Your code stays with you. The command line tool runs on your machine. On GitHub it reads code only, on the repositories you choose, and keeps findings, not code, with keys and passwords masked. Privacy policy
  • An open method. Every scan ends with a grade from A+ to F, worked out by a published, versioned method.

Start with one repository.

npx @hardkeel/quantum-scan
Or install on GitHub Questions: support