The Cyber Resilience Act: what does it mean for your software?

The Cyber Resilience Act (CRA) sets requirements for products with digital elements placed on the EU market, software included. The duty to report exploited vulnerabilities has applied since 11 September 2026, the rest applies from 11 December 2027. We show with proof what your code says about vulnerable components, secrets and tests, but we don't make you compliant.

Updated

Who the CRA applies to

The CRA addresses manufacturers, importers and distributors of products with digital elements made available on the EU market. The European Commission writes that products not made available on the market are not covered, and that open source counts under conditions.

Whether your product falls under it depends on what you make and how you offer it. We aren't lawyers: read the Commission's explanation and take legal advice if needed.

What the CRA asks of manufacturers

The Commission lists, among other things, a cybersecurity risk assessment, and a duty to report vulnerabilities and severe incidents: an early warning within 24 hours and a main notification within 72 hours. The regulation also asks you to keep track of the components in your product, among other things with a software bill of materials (SBOM).

Which evidence from your code and CI helps

A check doesn't make you compliant, but the questions can be answered with evidence:

  • Which components have a known vulnerability, from your lockfiles
  • Whether there are secrets in your code or history
  • Whether tests ran before a release: we read the evidence from your own CI
  • Whether it is described how you handle vulnerabilities and how you recover after an outage

What we don't do

We don't assess your product for CE marking, don't do a conformity assessment and don't report anything to a regulator. We don't deliver an SBOM either. You get findings with proof; what you do with them is up to you.

Questions we often get

Does my software fall under the CRA?

That depends on what you make and whether you place it on the EU market. The European Commission explains who the regulation applies to; the sources are below this page.

Do you make us CRA compliant?

No. A check alone makes nobody compliant. It shows with proof how your software stands, so you know what to look into.

Do you deliver an SBOM?

No. We show which components have a known vulnerability. We don't produce a full software bill of materials.

How is it different from NIS2?

NIS2 puts a duty of care on organisations in certain sectors. The CRA sets requirements for the products themselves. If you build software for such organisations, both can apply.

Does the CRA apply to open source?

Open source made available on the market is covered, with exceptions. The Commission explains the exceptions; we don't.

Sign up for the pilot

The pilot is by invitation. Sign up, we check whether your application fits and email you. You connect your repository with read access only, the first check starts by itself, you see what is checked and what is proven, and then we ask what it is worth to you. Have a question first? Ask it in the message below.

Our team

Reads every sign-up and every question

Our team reads what you send and answers by email. A conversation only happens if you ask for one: with the people who do the work, not a salesperson.

We only use your details to respond to your sign-up. The website doesn't keep your request.