The CRA and open source: what developers should know
By SBOMBox SBOM experts · · Updated · 4 min readShort answer: open source that nobody monetises is outside the Cyber Resilience Act, and individual contributors are not regulated. Open-source software stewards, such as foundations that support projects intended for commercial use, have a light set of duties and cannot be fined. Companies that ship open source inside a product they sell carry full responsibility for it: they must do due diligence on each component, report vulnerabilities upstream and fix them in their product.
When open source is in scope
The CRA regulates products made available on the market in the course of a commercial activity. The recitals explain how that applies to open source:
the provision of products with digital elements qualifying as free and open-source software that are not monetised by their manufacturers should not be considered to be a commercial activity.
Recital 18 adds that receiving funding or contributions from companies does not on its own make a project commercial, nor do regular releases. Development by not-for-profit organisations that reinvest all earnings after costs is not commercial. People who contribute code to projects they are not responsible for are not covered at all.
| Situation | CRA position |
|---|---|
| A hobby or community project published on GitHub | Out of scope |
| A library maintained by a company and released without monetisation | Generally out of scope; the deciding test is whether the manufacturer monetises it |
| A foundation that systematically supports projects intended for commercial use | Open-source software steward: light-touch duties under Article 24 |
| Open source sold, or monetised by its manufacturer | In scope as a product: full manufacturer duties |
| Open-source components inside a product a company sells | The company selling the product is responsible for them as its manufacturer |
What open-source stewards must do
A steward is a legal person, other than a manufacturer, with the purpose of 'systematically providing support on a sustained basis' for free and open-source software 'intended for commercial activities' (Article 3(14)). Under Article 24, stewards must:
- Put in place and document a cybersecurity policy that fosters secure development and effective vulnerability handling, encourages voluntary reporting, and promotes sharing information about discovered vulnerabilities in the community.
- Cooperate with market surveillance authorities on request and provide that policy to them.
- Report actively exploited vulnerabilities under Article 14(1) to the extent they are involved in developing the product, and severe incidents affecting their own systems that support it.
Stewards cannot receive administrative fines for any infringement of the CRA (Article 64(10)(b)).
If you ship open source inside your product
manufacturers shall exercise due diligence when integrating components sourced from third parties so that those components do not compromise the cybersecurity of the product with digital elements, including when integrating components of free and open-source software
Two further duties follow. When you find a vulnerability in a component, including an open-source one, you must report it to whoever manufactures or maintains that component and remediate it in your product. If you write a fix, you must share the relevant code or documentation with the maintainer (Article 13(6)).
- Know exactly which components and versions you ship, including transitive dependencies. That is the job of the SBOM.
- Check component health: maintenance activity, known vulnerabilities, security policy and licence.
- Prefer components whose maintainers publish SBOMs and advisories; see how to get SBOMs from suppliers.
- Monitor every shipped version for new vulnerabilities for the whole support period.
- Keep a record of upstream reports and patches you contributed, as evidence of due diligence.
You can see what your SBOM already records about your open-source components with the free SBOM checker.
Frequently asked questions
Does the CRA apply to open-source software?
Only when it is made available in the course of a commercial activity, which for open source means it is monetised by its manufacturer. Non-monetised open source and individual contributors are out of scope.
What is an open-source software steward?
A legal person, other than a manufacturer, that systematically supports free and open-source software intended for commercial use on a sustained basis, such as some foundations. Stewards have light duties under Article 24 and cannot be fined.
Am I responsible for open-source libraries in my product?
Yes. As the manufacturer you must exercise due diligence on third-party components, including open source, report vulnerabilities you find to the maintainers, and fix them in your product.
Does accepting company sponsorship make my open-source project commercial?
Not on its own. Recital 18 says financial support or contributions from manufacturers, and regular releases, do not by themselves make the activity commercial.
This is general information, not legal advice. Confirm how the rules apply to you with counsel.