CRA reporting needs an inventory that already exists.
Under the Cyber Resilience Act, the 24-hour clock starts when you become aware of an actively exploited vulnerability. Earnie keeps a record of what each release contains, built from the code rather than the manifest, so the first question of a report is a lookup.
Request a demoThe CRA clock is already running
Hours to an early warning
After becoming aware of an actively exploited vulnerability or severe incident.
Hours to a full notification
The second stage of an Article 14 report.
Full application
From 11 December 2027, including the Annex I requirements.
Top fine tier
Or 2.5% of worldwide annual turnover, whichever is higher.
Source: Regulation (EU) 2024/2847, the Cyber Resilience Act, Articles 14, 64 and 71.
From the code to a CRA report
Article 14 gives a manufacturer 24 hours to say which products are affected. Earnie keeps that answer ready in five connected steps.
Build the inventory from the code
Earnie reads declared dependencies and fingerprints every file, so it also finds code that never reached a manifest.
Illustrative example
See which vulnerabilities apply
Each known vulnerability is one row per component version. You state whether your product is affected, and Earnie publishes that as VEX.
- CVE
- CVE-2021-44228KEV
- Component
- log4j-core 2.14.1
- Severity
- Critical
- Fixed in
- 2.15.0
- Why it’s here
- Declared dependency
Illustrative example
Answer which releases are affected
Every release keeps its own frozen SBOM, so finding the affected versions is a lookup, not a rebuild from memory.
Illustrative example
Stop new exposure at the merge gate
Vulnerability policies run in developer self-checks and pull request scans, so a known exploited component is caught before it ships.
GitHub can enforce the result as a required status check. GitLab is currently advisory.
Export the CRA evidence package
The CRA package freezes one scan and makes every file from it, with a README that cites the clause each file supports.
Annex I, Part II(1)cryptographic assetsmerge gate, vulnerabilities, licenceschecksums and citationsWhat the CRA asks for, and when
Entry into force
The regulation is published and the transition period starts.
In forceConformity assessment bodies
The rules for notified bodies apply.
AppliesArticle 14 reporting
Early warning within 24 hours, notification within 72, through the ENISA Single Reporting Platform.
AppliesFull application
Annex I requirements, technical documentation and CE marking.
Next
Pick a clause to see what it asks for and what Earnie gives you.
An evidence layer for your CRA programme
Inventory
Build a per-release component inventory from code and manifests.
Assess
Review known vulnerabilities and record VEX statements.
Govern
Apply vulnerability and cryptography policies before code merges.
Record
Freeze snapshots and export the CRA package on demand.
Whether a product is in scope, and whether it meets the CRA, is a judgement for the manufacturer and its advisers. Earnie doesn’t file Article 14 reports or carry out conformity assessment. It keeps the inventory, the vulnerability statements and the record those activities depend on.
Questions about the CRA and Earnie
Does Earnie make us CRA compliant?
No tool can do that on its own. Earnie produces evidence toward your CRA obligations: a current, defensible record of the components, models and cryptography in your software. Whether a product is in scope, and whether it meets the regulation, is a judgement for the manufacturer and its advisers.
What does the CRA require for an SBOM?
Annex I, Part II asks manufacturers to identify and document the components in a product, including a software bill of materials in a commonly used, machine-readable format that covers at least the top-level dependencies. The SBOM forms part of the technical documentation and doesn’t have to be made public.
Why build the SBOM from the code rather than from manifests?
A manifest records what developers declared. Libraries copied into the tree, functions pasted from public repositories and code reproduced by coding agents never appear there. Earnie reads the manifests and also fingerprints every file, so the inventory reflects what the product contains.
How does Earnie help with Article 14 reporting?
Article 14 has applied since 11 September 2026. It asks for an early warning within 24 hours of becoming aware of an actively exploited vulnerability, and a notification within 72 hours. Earnie keeps an inventory for each release and flags vulnerabilities on the CISA Known Exploited Vulnerabilities list, so finding the affected releases is a lookup. Earnie doesn’t file the report itself.
Can we tell recipients which vulnerabilities don’t affect our product?
Yes. On a project’s Vulnerabilities page you state, for each known vulnerability, whether the product is under investigation, affected, not affected or fixed. Not affected needs a justification and Affected needs an action statement. Earnie publishes what you state as VEX, so the people who scan your SBOM can stop flagging what doesn’t apply.
What is in the CRA compliance package?
A CycloneDX SBOM, a CRA SBOM annex of cryptographic assets when you have cryptography scanning, and a compliance report covering the merge gate, vulnerabilities and licence obligations. They come from one frozen scan in one ZIP, with a README that lists checksums and the clauses each file is evidence for. The package is evidence, not a conformity claim.
Does my code leave my environment?
No. Earnie runs on your own server and reads your code there. On SaaS, only fingerprints, one-way hashes of your code, go to the knowledge base we host. On-prem, nothing leaves your network.
Have the answer before the clock starts.
See Earnie build a per-release inventory on code like yours.
Request a demo