NIST's draft plan deprecates RSA-2048 and P-256 after 2030 and disallows all RSA and ECC after 2035.
This is a preliminary CBOM. Get the full CBOM to complete your record.
A deeper scan of your code picks up where the SBOM stops. It finds crypto the manifest doesn't name, shows which of it your code can reach, and records how it is configured.
The full scan finds crypto the SBOM cannot name, including standard-library crypto.
The full scan confirms what your code actually calls, not just what a library could do.
The full scan captures your own code's configuration: mode, padding and key length.
The full scan brings the certificates and key material in your repositories into scope.
code-level detectioncrypto the manifest doesn't name
reachabilitywhich crypto your code can reach
mode · padding · key lengthfrom call sites
certificates · key materialfound in your code
dependenciescrypto in third-party packages
audit recordevery decision, for the auditor
This page checked one SBOM once. Your coding agent can check every change.
Earnie exposes the same cryptographic detection and your policies over MCP. The agent calls Earnie before it hands code back, so a quantum-vulnerable dependency is caught at the point of creation.
This SBOM holds {{ foundCount }} components. The browser tool stops at {{ capLabel }}, which is what keeps it free and unauthenticated. Nothing was truncated and nothing was sent.
A full inventory at this size runs as a scan against your repository, where component resolution is not the limiting factor.
A first-pass cryptographic inventory derived from your SBOM. It shows the scope of the crypto in your code before a deeper scan produces the full record.
{{ depsLabel }}
Dependencies with cryptography
of {{ analysedLabel }} components analysed
{{ algoCountLabel }}
Algorithms
{{ safeLabel }}
Quantum-safe
{{ vulnLabel }}
Quantum-vulnerable
{{ familyLabel }}
{{ legacyLabel }}LEGACYdeprecated or weak for classical reasons
{{ unaffectedLabel }}NO QUANTUM BREAKsymmetric and hash: weakened, not broken
Below are the first {{ previewCap }} of each, as CycloneDX cryptographic assets. Open a row for its details. Hollow fields exist in the schema and the full CBOM fills them; hover one to see what fills it.
This is a preliminary CBOM. Get the full CBOM to complete your record.
A deeper scan of your code picks up where the SBOM stops. It finds crypto the manifest doesn't name, shows which of it your code can reach, and records how it is configured.
The full scan finds crypto the SBOM cannot name, including standard-library crypto.
The full scan confirms what your code actually calls, not just what a library could do.
The full scan captures your own code's configuration: mode, padding and key length.
The full scan brings the certificates and key material in your repositories into scope.
code-level detectioncrypto the manifest doesn't name
reachabilitywhich crypto your code can reach
mode · padding · key lengthfrom call sites
certificates · key materialfound in your code
dependenciescrypto in third-party packages
audit recordevery decision, for the auditor
This page checked one SBOM once. Your coding agent can check every change.
Earnie exposes the same cryptographic detection and your policies over MCP. The agent calls Earnie before it hands code back, so a quantum-vulnerable dependency is caught at the point of creation.