✦ ENTERPRISE PQC READINESS
Find the crypto.
Plan the change.
Find where your code may need updates for quantum threats. See what to review first and get a clear action plan. Start with a public GitHub repository.
NOT SURE WHAT TO SCAN?
Try a real example: golang-jwt/jwt ↗A Go library for signing and verifying tokens. Scan it to see RSA and ECDSA findings, source locations and suggested next steps.
These are migration-planning signals, not evidence that this project is currently insecure. Results reflect the revision scanned.SCAN RESULTS
What needs your attention
THE TAKEAWAY
Your next steps
Turn these findings into a plan
Group related changes, identify the teams involved and define the checks needed before rollout.
Create my migration plan →
Add details about your application
Context applies to this assessed system. Split systems into separate assessments when their context differs. Keep secrets and personal data out of notes.
More download options
Save to a private workspace
Single operator workspace. Server saves include finding evidence, context and review notes. The access token grants access to all saved assessments; this is not a multi-tenant account.
See the code behind these findings
Select a finding to see its source location, suggested change and verification steps.
Red = migration concern or clearly weak cipher. Orange = verify use or configuration. Green = no post-quantum migration flag for that observation, not a general security guarantee.
What was checked & limitations
Technical tools and local file upload
Saved assessments
Your assessments
Save up to ten assessments on this browser and device. Findings and notes are accessible to anyone using this browser profile. No account sync; clearing browser data removes saved copies.
Already have a cryptography inventory?
Upload a list of the encryption, digital signatures and other cryptography used in your software. This is called a Cryptographic Bill of Materials (CBOM). We’ll turn it into a review checklist and action plan. The file is processed in this local workspace; we do not scan your source code during import.
Which files can I upload?
Use a CBOM JSON file in CycloneDX 1.6 or 1.7 format, exported from a tool such as CBOMkit. The results depend on what the original tool found.
For technical users: scanner coverage
Coverage you can inspect
Unsupported APIs, runtime protocols and indirect calls can be missed. Language count is not a measure of detection accuracy.
Request a scoped engagement covering inventory review, migration priorities and a customer decision brief. Scope, reviewer availability and price are agreed before payment.