Earnie

Turn your SBOM into a CBOM.

Find the cryptography in what you ship. Export as CycloneDX 1.7.

Drop your SBOM here
or choose a file ·
CycloneDX or SPDX · Up to 500 components · 5 MB
ANALYSED IN MEMORY. NOTHING STORED. NO SOURCE CODE UPLOADED.
Can’t share your SBOM? Talk to us under NDA →

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.
Ready for the full CBOM? Talk to us
IN THE FULL CBOM
  • 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.

SBOM to CBOM converter, free CBOM generator | Earnie
Earnie

Turn your SBOM into a CBOM.

Find the cryptography in what you ship. Export as CycloneDX 1.7.

Drop your SBOM here
or choose a file ·
CycloneDX or SPDX · Up to 500 components · 5 MB
ANALYSED IN MEMORY. NOTHING STORED. NO SOURCE CODE UPLOADED.
Can’t share your SBOM? Talk to us under NDA →
NOT A READABLE SBOM

{{ invalidMessage }}

Accepted: CycloneDX JSON (1.4–1.7), SPDX JSON (2.2–3.0), SPDX tag-value.

OVER THE COMPONENT CAP

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.

Run a full scan
RESOLVING {{ doneCount }} / {{ totalCount }} COMPONENTS
{{ currentPurl }}
Component metadata only. No source, no archives, no file contents.
{{ errorTitle }}

{{ errorMessage }}

Contact us →

NIST's draft plan deprecates RSA-2048 and P-256 after 2030 and disallows all RSA and ECC after 2035.

RESULT · {{ analysedLabel }} COMPONENTS ANALYSED · 0 CRYPTOGRAPHIC ASSETS MATCHED

No cryptography found in your SBOM's packages. That doesn't mean there is none.

This check only sees the packages your SBOM names. Crypto from the standard library, or inside your own code, never appears in a manifest.

A full scan reads your source code. It finds each crypto call, with its mode, padding and key length.

Scan the source instead
PRELIMINARY CBOM {{ sourceLabel }}

Your preliminary CBOM

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 }} LEGACY deprecated or weak for classical reasons
{{ unaffectedLabel }} NO QUANTUM BREAK symmetric and hash: weakened, not broken
{{ unassessedLabel }} NOT ASSESSED no curated verdict yet

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.

{{ specLabel }}
{{ validLabel }}

ALGORITHMS

{{ algosShown }}
  • {{ a.name }} {{ a.levelLabel }}
    {{ a.param }} primitive: {{ a.primitive }} algorithmFamily: {{ a.family }} occurrences: {{ a.occurrences }}
    evidence → {{ a.source }}
    modeCBC, GCM or CTR is chosen in code. A source scan resolves it. paddingSet per call. A source scan resolves it.

DEPENDENCIES

{{ depsShown }}
  • {{ d.purl }} {{ d.countLabel }}
    dependsOn → {{ d.refsLabel }}

PROTOCOLS

{{ protosShown }}
  • {{ p.name }} type: {{ p.type }}
    version: {{ p.version }}
    evidence → {{ p.source }}

Get the full report as a PDF

{{ gateSummary }}

{{ emailError }}
REPORT READY

Your PDF is downloading.

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.
Ready for the full CBOM? Talk to us
IN THE FULL CBOM
  • 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.