Key facts
- Open source in scope when
- Made available in the course of a commercial activity
- Not monetised
- Outside the CRA as a product
- Steward obligations
- Article 24, a lighter regime
- Fines for stewards
- None (Article 64(10))
- Shipping open-source components
- The manufacturer of the final product is responsible for them
When open source is in scope
The test is the same as for any product: is it made available on the EU market in the course of a commercial activity? For open source, the regulation adds a clarification. Providing free and open-source software that isn’t monetised by its manufacturer isn’t a commercial activity. So a hobby project, a library maintained in your spare time or a tool published by a research group sits outside the CRA as a product.
Monetisation changes that. Selling the software, charging for a hosted version that the software needs, or selling paid features turns the same code into a product made available commercially.
Three roles
| Role | Who | What the CRA asks |
|---|---|---|
| Manufacturer | Whoever places the product on the market commercially, including a company selling open-source software | All manufacturer obligations: Annex I, documentation, conformity assessment, Article 14 reporting |
| Open-source software steward | A legal person, other than a manufacturer, that systematically supports open source intended for commercial use, such as a foundation | A lighter regime in Article 24, with no administrative fines |
| Contributor | Anyone sending code to a project they don’t control | No obligations under the CRA for that contribution |
The same organisation can hold different roles for different things. A company can be the manufacturer of its paid product and the steward of the open-source project the product is built on.
What stewards have to do
Under Article 24, a steward puts in place and documents a cybersecurity policy that fosters the secure development of the software and the handling of vulnerabilities, cooperates with market surveillance authorities when asked, and takes part in reporting to the extent it is involved in the development. Stewards aren’t subject to administrative fines.
If you ship open-source components
For most indie developers, open source enters the picture as dependencies. Here the rules are clear: the manufacturer of the final product is responsible for all of it.
- Due diligence. Article 13 asks you to exercise due diligence when you integrate third-party components, open source included, so they don’t compromise the product’s security.
- Inventory. List them in your software bill of materials.
- Report upstream. If you find a vulnerability in a component, report it to the person or project maintaining it, and share the fix if you wrote one.
- Keep updating. A vulnerable dependency is a vulnerability in your product, for the whole support period.
What to do now
- If your project isn’t monetised, nothing changes for it as a product. A clear
SECURITY.mdis still good practice. - If you sell something built on your own open-source project, treat the paid product as in scope and check whether it is in the default category.
- If your organisation supports a project others build products on, look at whether you act as a steward under Article 24.
Questions
Does publishing my library on GitHub make me a manufacturer under the CRA?
Not if the project isn’t monetised. Free and open-source software made available outside a commercial activity isn’t in scope as a product. Contributing to someone else’s project doesn’t make you its manufacturer either.
Does accepting donations make an open-source project commercial?
Generally not. The recitals say that accepting donations without making a profit shouldn’t count as a commercial activity. Charging for the software, or for features of it, is different. The Commission’s draft guidance from March 2026 goes through edge cases.
What is an open-source software steward?
A legal person, other than a manufacturer, that provides sustained support for the development of specific open-source products intended for commercial activities, such as a foundation. Stewards have a lighter set of duties under Article 24 and can’t receive administrative fines.
I ship open-source packages in my paid app. What do I have to do?
You are the manufacturer of the app, so you are responsible for its components, open source included. Exercise due diligence when you pick them, list them in your SBOM, and report vulnerabilities you find in a component to whoever maintains it.
Sources
- Regulation (EU) 2024/2847, Articles 13, 24 and 64 and recitals, EUR-Lex
- Cyber Resilience Act: open source, European Commission
This guide explains the regulation in general terms. It isn’t legal advice for your product.