> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanoss.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Earnie for PQC & Crypto Leads

> The migration starts with an inventory: what runs, not just what appears, and what won't survive the transition.

You never run a scan. You consume the record.

## "Which of Our Algorithms Won't Survive the Transition?"

The Dashboard's [Post-Quantum Exposure](/en/latest/earnie/using-earnie/dashboard#post-quantum-exposure) card assesses every cryptographic asset type by its resolved algorithm family, counting only the classical public-key families a quantum computer actually breaks, so a broken hash like MD5 is a severity problem here, never a migration item. Assets Earnie couldn't judge stay separate as unassessed, they're never folded into the quantum-safe remainder.

## What Runs, Not Just What Appears

Every [cryptographic finding](/en/latest/earnie/using-earnie/triaging-findings#cryptographic-findings) carries a reachability verdict, reachable, not reached, or unknown, so the migration list is the code that actually runs in a call path, not everything the scanner noticed. When there's a path, **View call trace** opens it, entry point first.

## The Inventory, Exported

Generate a [CBOM](/en/latest/earnie/evidence/exporting-sboms) with cryptographic assets included to get the full inventory as a versioned artifact, alongside the [Export-control evidence report](/en/latest/earnie/evidence/exporting-sboms#the-export-control-evidence-report) when your organisation is entitled to it.

## What's Next

Open the [Dashboard](/en/latest/earnie/using-earnie/dashboard) for post-quantum exposure at a glance, or [Exporting an SBOM](/en/latest/earnie/evidence/exporting-sboms) to generate a CBOM.
