EU Cyber Resilience Act
Cyber Resilience Act checks: CRA File
Check your product, your SBOM and your security contact against the Cyber Resilience Act, for free and in your browser. The generator for the technical file, the declaration of conformity and the vulnerability reports is next.
An SBOM (software bill of materials) is the list of parts your software is built from: the libraries and their versions. The Act expects you to keep one.
Free. No account. Nothing is uploaded.
- passMachine-readable format: CycloneDX 1.5
- passComponents listed: 2 components
- passComponent name and version: 100 % have both
- passUnique identifier (package URL): 100 % have a purl
- missingSupplier name: 50 % name a supplier
- passDependency relationships: 1 entry describes who depends on whom
- passAuthor of the SBOM data: cdxgen
- passTimestamp: 2026-10-05T10:00:00Z
- passTop-level product identified: my-app
The dates that matter
Reporting is live. Manufacturers must report actively exploited vulnerabilities and severe incidents, including for products already on the market: early warning in 24 hours, notification in 72 hours, final report later, to the CSIRT and ENISA through the single reporting platform (Article 14).
The main obligations apply. Technical documentation, the EU declaration of conformity, conformity assessment, CE marking and the vulnerability handling requirements.
Free tools
Repository check
Paste a GitHub repository. No SBOM to prepare: we read the public data and show what is already in place and what is missing.
New · runs in your browser
Licence notices
Drop an SBOM and get a THIRD-PARTY-NOTICES file, a licence overview and the copyleft risks for your project licence.
New · runs in your browser
Product classifier
Five questions: is the product in scope, which category does it fall in, and which conformity route follows.
Annex III and IV, Art. 32
SBOM checker
Drop a CycloneDX or SPDX file and see which minimum elements are missing. Optional lookup of known vulnerabilities.
Runs in your browser
security.txt and policy
The contact file and the coordinated disclosure policy the Regulation expects, ready to publish.
RFC 9116
Guides
- CRA for open-source maintainers and stewards: what applies: Does the Cyber Resilience Act apply to your open-source project? Commercial activity, the steward role (Articles 3 and 24), what a steward must do and what a maintainer who is not a steward owes.
- CRA important and critical products: the full Annex III and IV list: Which products are important Class I, Class II or critical under the Cyber Resilience Act, the full lists from Annex III and Annex IV, and what the class means for conformity assessment.
- CRA manufacturer, importer or distributor: which are you: Who counts as manufacturer, importer or distributor under the Cyber Resilience Act, when an importer or distributor is treated as a manufacturer, and what each role has to do.
- CRA reporting obligations: 24 hours, 72 hours, final report: What the Cyber Resilience Act requires you to report, when (24 hours, 72 hours, 14 days or one month), to whom, and what each report should contain. Applies from 11 September 2026.
- CRA SBOM requirements: NTIA minimum elements vs BSI TR-03183-2: What the Cyber Resilience Act says about a software bill of materials, what the NTIA minimum elements and the German BSI technical guideline TR-03183-2 add, and a field-by-field comparison.
- CRA support period: how long, and what to publish: How long must a manufacturer provide security updates under the Cyber Resilience Act? The five-year default, the ten-year availability rule, and what to tell users (Article 13(8), 13(9), 13(19)).
- EU declaration of conformity template for the Cyber Resilience Act: What an EU declaration of conformity under the Cyber Resilience Act contains (Annex V), the simplified version (Annex VI), and a fill-in template with the fields explained.
- SBOM on GitHub releases for the CRA: what to attach: Does the Cyber Resilience Act require you to attach an SBOM to each GitHub release? What Annex I Part II and Annex VII require, what they do not, and a practical release routine.
- SECURITY.md or security.txt for the CRA: which one: Which file covers the Cyber Resilience Act's vulnerability reporting contact: SECURITY.md, security.txt or both? What Annex I Part II and Annex II require and what they leave open.
- Vulnerability disclosure policy template for the Cyber Resilience Act: A coordinated vulnerability disclosure policy template and a security.txt walk-through, with what the Cyber Resilience Act expects (Annex I, Part II) and how to publish both.
In your pipeline
The same checks run from the command line and in GitHub Actions. Nothing leaves your machine unless you ask for a vulnerability lookup.
npx @ambolt/cra sbom bom.json --osv --min 7
npx @ambolt/cra licences bom.json --project proprietary
npx @ambolt/cra repo owner/name
- uses: ambolt-dev/cra-check@v1
with:
sbom: bom.json
min-checks: 7
project-licence: proprietary
@ambolt/cra on npm · cra-check on GitHub.
What the generator will produce
Technical file
The Annex VII documentation assembled from your SBOM and a few answers.
Declaration of conformity
The full and the simplified EU declaration, with your product details filled in.
User information
Support period, security contact and update instructions as Annex II asks.
Report drafts
The 24-hour, 72-hour and final reports with countdown reminders.
Release updates
Regenerate the file on every release from the command line or CI, so it never drifts from the product.
Component watch
A daily check of your components against new vulnerabilities. Only component names are stored.
Planned plans
Not on sale yet. The free tools above stay free.
Free
$0
- Classifier
- SBOM checker
- security.txt and policy
Pro
$29 / month
- One product
- Technical file and declaration
- Report drafts
- Component watch
Team
$99 / month
- Ten products
- CI integration and API
- Several users
File pack
$199 once
- One product
- The documents, no monitoring
Information generated from your inputs, with article references to Regulation (EU) 2024/2847. It is not legal advice and does not replace your own assessment; check the references against the Official Journal.