Quantum

Cryptography comes into view.

CLI · Beta

Find encryption in source code

Where and how does your software encrypt data? The local scanner finds encryption, signatures, hash algorithms and key material. You receive precise locations, a risk assessment and a clear inventory.

For development and security teams that want to understand what they use today and what needs to change for a post-quantum future.

Findings by file and line

For example: where does your project use AES-GCM to encrypt data?

Where an algorithm is called

Quantum shows you supported algorithms such as AES-GCM for encryption, RSA for signatures or MD5 for hashing. Recognised risks and the rest of the inventory are reported separately.

Eight languages, clear boundaries

From Python to C#. The selection shows examples, from older algorithms to post-quantum cryptography.

Python
Examples of recognised algorithms
  • MD5
  • SHA-1
  • RSA
  • ECDSA
  • AES-GCM
  • SHA-3
  • ML-KEM
  • ML-DSA
  • SLH-DSA
  • FN-DSA
  • HQC
  • FrodoKEM
What Quantum does not detect

Quantum recognises supported libraries and code patterns. Custom helper functions or settings loaded only at runtime may go undetected. Finding an algorithm shows that it appears in the code; its secure use needs a separate assessment.

Risk assessment from 0 to 100

Which findings need attention first? Quantum distinguishes algorithms already considered broken from risks posed by future quantum computers. The score helps you prioritise, while the rest of the inventory stays visible separately.

0–100Points, not a percentage

The highest assessed individual score determines the project score.

The assessment considers the algorithm, its role, assumed lifetime and exposure. Inventory entries without a recognised risk assessment, along with key and certificate findings, do not increase the score.

Algorithm
The recognised risk
Exposure
CLI assumption: internet
Lifetime
How long protection is needed
Use
Its role in the code

Reports for your team and your CI

Share the inventory with your team. Transcendence uses it to plan the migration; Anchor records it as evidence.

Directly in the command line

You can read the risks, inventory and findings in German or English.

Risks · Inventory · Scan scope
Integrate into CI

Quantum can be integrated into your CI, the automated checks for your project. You can set a risk threshold. Incomplete scans are reported separately and do not count as a successful check run.

--schwelle
Complete scan coverage required: exit 4 for incomplete coverage, exit 1 above the threshold.
--vollstaendig-verlangt
Mark incomplete runs with exit code 4.
--nur
Inspect an explicit list of whole files.

Test Avalanche in the beta

Questions about Quantum

What is Avalanche Quantum?

Quantum is a local scanner for cryptography in source code. It recognises supported encryption calls, signatures, hash algorithms and key material in eight languages. It provides precise locations, a risk assessment and a separate inventory, including current and post-quantum algorithms.

Does Quantum only find outdated encryption?

No. Quantum also records current encryption, such as supported AES-GCM calls, as well as post-quantum algorithms. Risks and other inventory entries are kept separate. This lets you see both potential problems and the full recognised inventory.

Which programming languages does Quantum support?

Python, JavaScript, TypeScript, Java, Go, C, C++ and C#. Detection covers selected libraries and code patterns. The report helps you assess which parts of the project were actually examined.

Does my source code stay on my machine?

The analysis itself runs locally. Quantum neither executes nor changes your code. The initial installation may require an internet connection. Beta diagnostic data is anonymised on your device before it is transmitted to MK Groups Schweiz; requesting access does not activate any transmission.

Does a risk score of 0 mean my project is quantum-safe?

No. The score refers to recognised risks within the scanned scope. It does not rule out undetected algorithms. Key and certificate findings and gaps in the scan are reported separately.

What is a CBOM?

A CBOM is a bill of materials listing the cryptographic components of a piece of software, such as its encryption and signature algorithms. Quantum exports it as CycloneDX 1.6 JSON. Alternatively, you can use a text report or the detailed JSON v2 report.

Which system can I use to evaluate Quantum?

The primary target is Linux x64 with Node.js 24. Support for other platforms is confirmed separately for each package version.

Does Quantum change my code?

No. Quantum analyses and documents. Transcendence handles planning and supported migration steps; Anchor provides the evidence. All three products launch together. Quantum offers a command line and a local offline report viewer.

AVALANCHE Quantum

Your details

Title optional

Non-binding request. No payment and no automatic activation of the software. Your details are used to assess and answer your request; this does not sign you up for marketing. Privacy