Guide
Open-source software and the Act
Contributing code does not make you a manufacturer. Responsibility depends on who publishes and controls a project, and on whether it is supplied commercially.
Last reviewed against European Commission, National Cyber Security Centre Ireland and cyberresilienceact.eu. Sources

The basics
Stewards and manufacturers
Commercial lines
What the guidance says
The Commission's final guidance, as summarised by Hogan Lovells Cadwalader, makes three points [7].
Contributors
Contributing code does not by itself make someone a manufacturer or a steward. It depends on who publishes and controls the project [7].
Community and paid editions
A community edition can remain outside commercial scope even if a paid edition exists [7].
Services
Separately sold consulting or training does not by itself make the software commercial [7].
For your products
Using community code
If you build on open-source libraries, you carry the product duties for what you ship. If a vulnerability stems from a third-party component, you must inform its maintainer and share any patch [5]. A report to the authorities is needed only where the flaw is actively exploited in your own product [7].
Keep a trail to the maintainer
Record who maintains each component and how you reach them. The duty to pass on a patch is hard to meet if you cannot identify the project.

Practical steps
Before December 2027
Compile an inventory of components, because techUK links vulnerability handling to producing a software bill of materials [8]. Then decide, per component, who watches for advisories and who contacts the maintainer. Where the same library appears in several products, assign one owner so that a single advisory does not trigger several uncoordinated responses.
The supplier oversight guide covers contractual controls, and the software guide covers scope.
Keep reading
Read next
Support period
How the Cyber Resilience Act sets support periods and update availability, and how the Commission guidance treats versions and upgrades.
Read the guide
UK manufacturers
How the EU Cyber Resilience Act reaches UK manufacturers without an EU office: authorised representatives, importers, where reports go and open questions.
Read the guide
UK comparison
How the EU Cyber Resilience Act and the UK PSTI product security regime differ in scope, duties and enforcement, and what the UK bill may add.
Read the guideHow CyPro can help
Need a hand getting ready?
Reading the rules is one job. Mapping them to your organisation, closing the gaps and showing the evidence are several more. CyPro's consultants can take any of them off your plate.
Fractional CISO for the board
A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.
More on cypro.co.uk
Penetration testing
A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.
More on cypro.co.uk
Hardening and segmentation
Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.
More on cypro.co.uk
24/7 security monitoring
Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.
More on cypro.co.uk
Incident response
If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.
More on cypro.co.uk
Vulnerability scanning
Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.
See the scanning service
Get ready
Need to know what this means for you?
Meeting the Act takes a named owner for product security, a decision path for reporting and a plan to 2027. A virtual CISO can take that role, assess which products are in scope and report progress to your board.