← CRA Glossary
CRA Regulatory

Open Source Steward

An Open Source Steward is a legal entity that systematically provides non-commercial support for open source software components used in products with digital elements. The CRA introduces a specific, lighter regulatory category for Open Source Stewards - they are not treated as manufacturers but have limited obligations to support coordinated vulnerability disclosure.

An Open Source Steward is a legal entity that systematically provides non-commercial support for open source software components used in products with digital elements. The CRA introduces a specific, lighter regulatory category for Open Source Stewards - they are not treated as manufacturers but have limited obligations to support coordinated vulnerability disclosure.

CRA Regulatory

Last updated 19 July 2026

What Is an Open Source Steward Under the CRA?

The EU Cyber Resilience Act introduces the category of 'Open Source Steward' to address the reality that much of the software infrastructure underlying commercial digital products is developed and maintained by non-commercial foundations, projects, and individuals. An Open Source Steward is a legal entity (such as a foundation or non-profit) that provides systematic support for the development of open source software intended for commercial use - but does not itself place products on the market for commercial purposes. The CRA explicitly excludes Open Source Stewards from the full range of manufacturer obligations. They are not required to perform conformity assessments, issue declarations of conformity, or affix CE marks. This was a significant concession made after open source community pushback during the CRA legislative process.

CRA reference:Article 3(14), Recital 19

What Obligations Do Open Source Stewards Have?

While Open Source Stewards are exempt from most CRA manufacturer obligations, they are not entirely unregulated. The CRA requires Open Source Stewards to:

  1. Establish and maintain a CVD policy - making it possible for security researchers and users to report vulnerabilities in the software they steward.
  2. Cooperate with market surveillance authorities - providing information relevant to the security of their software when requested.
  3. Notify ENISA of actively exploited vulnerabilities in their software components when they become aware of them.

These lightweight obligations reflect the CRA's recognition that open source stewards play a critical role in the software supply chain and need to participate in the EU's vulnerability management ecosystem, even if they are not commercial manufacturers.

CRA reference:Article 3(14), Article 24

The Open Source Steward Category in Practice

Major Linux distributions, package repositories like Apache Software Foundation, and foundations like the Eclipse Foundation and OpenSSF are the primary intended beneficiaries of the Open Source Steward category. These organisations maintain critical infrastructure software used in millions of commercial products but are not themselves placing products on the EU market. The category ensures they have a defined, proportionate regulatory status rather than being inadvertently classified as manufacturers. For commercial companies that both contribute to open source projects and manufacture products (a common pattern), the CRA requires careful organisational separation: the commercial product manufacturing activities are subject to full CRA obligations, while any separate non-commercial open source project support activities may qualify for the Open Source Steward classification.

CRA reference:Recital 19

Implications for Manufacturers Using Open Source Components

The existence of the Open Source Steward category does not reduce commercial manufacturers' obligations with respect to the open source components they incorporate in their products. Manufacturers remain fully responsible for ensuring that all components in their products - including open source ones - meet the CRA's essential requirements when integrated into the finished product. The CRA explicitly states that integrating an open source component into a commercial product does not transfer liability to the component's steward. This makes SBOM maintenance, continuous vulnerability monitoring of dependencies, and rapid response to upstream vulnerability disclosures essential practices for any manufacturer using open source components.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Does the Linux Foundation qualify as an Open Source Steward under the CRA?+

The Linux Foundation and similar foundations are the primary intended beneficiaries of the Open Source Steward category. However, formal qualification depends on the specific activities of each entity and project. An entity must systematically and non-commercially support open source software for the category to apply. Foundations with significant commercial membership funding may need to analyse their specific activities carefully to determine whether the Open Source Steward classification applies to each of their projects.

If I use a component maintained by an Open Source Steward, am I responsible for its security?+

Yes. As the commercial manufacturer of the finished product, you are responsible for ensuring all incorporated components meet the CRA's essential requirements. You cannot delegate this responsibility to the Open Source Steward. You must monitor the steward's security advisories, maintain a current SBOM that includes the component, and patch vulnerabilities in the component when they are disclosed. The Open Source Steward's CVD policy makes it easier for you to learn about vulnerabilities - but acting on them is your obligation.

Can a company that sells commercial support for open source software be an Open Source Steward?+

This is a grey area. The Open Source Steward category is explicitly for non-commercial support. A company that derives revenue from supporting or distributing an open source project may be treated as a manufacturer rather than a steward if that support constitutes placing products on the EU market for commercial purposes. Dual-licensing models (open source community edition + commercial edition) require careful analysis to determine which CRA category applies to which activities.

Sector checklists covering Open Source Steward

Embedded Linux DevicesEmbedded Linux devices span a vast range - from network gateways and industrial HMIs to set-top boxes and smart displays. All are products with digital elements subject to the CRA. The open-source nature of Linux creates specific obligations around SBOM completeness and CVE monitoring. The class follows the core functionality of each device (Article 7(1)). An industrial HMI is default class. A network gateway whose core functionality is a router is Important Class I (Annex III, point 12). Industrial or infrastructure use does not change the class.Open Source HardwareOpen source hardware (OSH) projects occupy a unique position under the CRA. The regulation explicitly excludes hardware developed for non-commercial purposes, shared freely without monetisation. However, when open source hardware designs are manufactured and sold commercially - even by small businesses or community projects - the CRA's full scope applies. The CRA also introduces a 'steward' concept for open source projects that is relevant to OSH ecosystems. Understanding the commercial/non-commercial boundary is essential.Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Open Source Steward fits into your complete CRA compliance programme.

View checklists →