Open-source software steward
Under the Cyber Resilience Act, open source projects can have a steward: typically a foundation or organisation that sustains a project without marketing it as a manufacturer. The regulation gives this role its own, much lighter set of duties.
Cyber Resilience Act open source steward: definition
Article 3(14) of Regulation (EU) 2024/2847 names four features: a legal person that is not a manufacturer, that systematically provides support on a sustained basis for the development of specific free and open-source products intended for commercial activities, and that ensures the viability of those products.
The duties in Article 24 are deliberately light. The steward puts in place a documented cybersecurity policy that fosters secure development and effective vulnerability handling, cooperates with market surveillance on request, and reports actively exploited vulnerabilities to the extent it is involved in development. It reports severe incidents insofar as they affect the network and information systems it provides for development.

Cyber Resilience Act open source in practice
The role fits open-source foundations and organisations that fund and maintain a project over time without selling it as a product. Individual developers contributing without commercial intent are not covered.
Article 64(10) rules out fines for stewards. The regulation relies on cooperation rather than penalties here.
A foundation maintains a widely used cryptography library that hundreds of manufacturers build into their products. It does not sell the library but ensures its continuity with dedicated maintainers and security processes. That makes it a steward. The manufacturers that embed the library remain fully responsible for their own products.
What to do
- Check whether the organisation meets the Article 3(14) criteria or is in fact a manufacturer
- Document the cybersecurity policy in a verifiable way and, as good practice, publish it with a channel for vulnerability reports
- Set up a process for reporting via the Single Reporting Platform
- Organise how you share discovered vulnerabilities with the community
Common misconceptions
“Every open-source project has a steward.”
Individuals or loose communities maintain many projects. Without a legal person systematically supporting development, the role does not exist.
“Selling open source makes you a steward.”
Anyone offering open-source software under its own name in the course of a commercial activity and monetising it is a manufacturer, with all the Article 13 obligations.
Related terms
Carries the full obligations, including for embedded open-source components.
Read the entryCoordinated vulnerability disclosure
A central part of a steward’s cybersecurity policy.
Read the entryActively exploited vulnerability
Stewards report these too, to the extent they are involved in development.
Read the entryWhere does your product stand on the Cyber Resilience Act?
The free Product Check shows within minutes which of your products are in scope. The Readiness Check shows how well your company is prepared for the obligations.
Free, no login, no email. See who is in scope or go straight to the compliance software.