[comment]: # (Compile this presentation with the command below) [comment]: # (mdslides lpw2026-ecosystem-steward.md --include ../media) [comment]: # (...or by running the Makefile with "make") [comment]: # (mdslides can be installed from https://github.com/dadoomer/markdown-slides/) ## What is an OSS Ecosystem Steward, and can we have one? London Perl & Raku Workshop 2026 Salve J. Nilsen (CPANSec, Oslo.pm) 🐘 Mastodon — [@sjn\@chaos.social](https://chaos.social/@sjn) Note: The EU Cyber Resilience Act (CRA) introduces a new entity dedicated to sustaining and securing Open Source projects: the OSS Steward. This organization is meant to support projects in many ways – including helping attest their software is intended for commercial use, and to be the single contact point towards market authorities, CSIRTs, and manufacturers wishing to remain CRA compliant. In many ecosystems, existing foundations may offer this help. But for Perl and CPAN, there is no central organization that is both capable and willing to assume the responsibilities of a Steward. So how can we still support all who intend to continue make, rely on, and benefit from OSS, Perl and CPAN? Here, Salve presents his solution – a non-profit community-owned cooperative: the OSS Ecosystem Steward.
## The concept, in three sentences
## The concept, in three sentences 1. A **community co-op**, owned by the people who look after our core projects, services and communities.
## The concept, in three sentences 1. A **community co-op**, owned by the people who look after our core projects, services and communities. 1. **Companies buy attestations** from maintainers, to help them be secure & compliant – and that money sustains the community.
## The concept, in three sentences 1. A **community co-op**, owned by the people who look after our core projects, services and communities. 1. **Companies buy attestations** from maintainers, to help them be secure & compliant – and that money sustains the community. 1. **Everyone retains full control**, and get the resources needed to both do compliance work and the rest.
## EU Cyber Resilience Act ### December 11, 2027
## EU Cyber Resilience Act ### December 11, 2027 Manufacturers are responsible for the security of _every_ component used in their products
## EU Cyber Resilience Act ### December 11, 2027 Manufacturers are responsible for the security of _every_ component in their products - …including the Open Source ones
## EU Cyber Resilience Act ### December 11, 2027 Manufacturers are responsible for the security of _every_ component in their products - …including the Open Source ones - …and the remote data processing solutions they rely on
## EU Cyber Resilience Act ### December 11, 2027 Manufacturers are responsible for the security of _every_ component in their products - …including the Open Source ones - …and the remote data processing solutions they rely on - …phone apps, servers, frameworks, libraries, everything!
## EU Cyber Resilience Act ### December 11, 2027 Manufacturers are responsible for the security of _every_ component in their products - …including the Open Source ones - …and the remote data processing solutions they rely on - …phone apps, servers, frameworks, libraries, everything! No transfer of liability – it stays with the manufacturer ([CRA FAQ 4.1.1](https://cra.orcwg.org/faq/official/faq_4-1-1/))
## CE product mark For _manufacturers_ wishing to place their _products_ on the _European market_. 
## CE product mark For _manufacturers_ wishing to place their _products_ on the _European market_. - The CE mark works _recursively_
## CE product mark For _manufacturers_ wishing to place their _products_ on the _European market_. - The CE mark works _recursively_ - Open Source is not allowed to use the CE mark!
## CE product mark For _manufacturers_ wishing to place their _products_ on the _European market_. - The CE mark works _recursively_ - Open Source is not allowed to use the CE mark! - "Open Source projects have no obligations under the CRA"

## Upstream implications - No known exploitable vulnerabilities ([Annex I, Part I](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#d1e47-68-1))
## Upstream implications - No known exploitable vulnerabilities ([Annex I, Part I](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#d1e47-68-1)) > The product must be **updatable** for its **entire support period**, including relevant updates from its Open Source components.
## Upstream implications - Support period matching expected use, e.g. 5 years ([Article 13(8)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.008))
## Upstream implications - Support period matching expected use, e.g. 5 years ([Article 13(8)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.008)) > Open Source components used in the product, or in its remote data processing solutions, should be **supported for the same period**.
## Upstream implications - Security updates available for 10 years ([Article 13(9)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.009))
## Upstream implications - Security updates available for 10 years ([Article 13(9)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.009)) > **Software update services** that depend on Open Source need to **stay secure** and available for the same period.
## Upstream implications - Correct and current metadata ([Article 64(4)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#064.004))
## Upstream implications - Correct and current metadata ([Article 64(4)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#064.004)) > This includes any **metadata provided in an SBOM**, which also must be kept current with upstream projects (e.g. tracking changes in ownership, project name, version number schema, license, etc.)
## Upstream implications - Fixes shared with upstream – someone has to receive them ([Article 13(6)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.006))
## Upstream implications - Fixes shared with upstream – someone has to receive them ([Article 13(6)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.006)) > Someone upstream **needs to be available to receive**, adopt and apply these fixes, ideally in a **timely manner**.
## Upstream implications We get _our own due diligence_ expectations, by implication, on _hundreds_ or _thousands_ of components
## A [Hobson's Choice](https://en.wikipedia.org/wiki/Hobson%27s_choice)
## A [Hobson's Choice](https://en.wikipedia.org/wiki/Hobson%27s_choice) #### **Accept** – demonstrate the project is _intended for commercial use_
## A [Hobson's Choice](https://en.wikipedia.org/wiki/Hobson%27s_choice) #### **Accept** – demonstrate the project is _intended for commercial use_ > …and take on boring, tedious compliance work
## A [Hobson's Choice](https://en.wikipedia.org/wiki/Hobson%27s_choice) #### **Accept** – demonstrate the project is _intended for commercial use_ > …and take on boring, tedious compliance work #### **Decline** – and risk users being forced to switch away
## A [Hobson's Choice](https://en.wikipedia.org/wiki/Hobson%27s_choice) #### **Accept** – demonstrate the project is _intended for commercial use_ > …and take on boring, tedious compliance work #### **Decline** – and risk users being forced to switch away > …with security consequences for everyone
## A [Hobson's Choice](https://en.wikipedia.org/wiki/Hobson%27s_choice) Our challenge: make _accepting_ the **realistic and fair** option
## The Open Source Software Steward
## The Open Source Software Steward A new legal category in the CRA ([Article 3](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_3), [Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)) - …a legal entity, but not a person or manufacturer
## The Open Source Software Steward A new legal category in the CRA ([Article 3](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_3), [Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)) - …a legal entity, but not a person or manufacturer - …_systematically_ supporting Open Source intended for commercial use
## The Open Source Software Steward A new legal category in the CRA ([Article 3](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_3), [Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)) - …a legal entity, but not a person or manufacturer - …_systematically_ supporting Open Source intended for commercial use - …ensuring the viability of those projects
## The Open Source Software Steward A new legal category in the CRA ([Article 3](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_3), [Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)) - …a legal entity, but not a person or manufacturer - …_systematically_ supporting Open Source intended for commercial use - …ensuring the viability of those projects Should be doable for _hundreds_ of projects, no?
## The Steward's obligations
## The Steward's obligations Light-touch obligations ([Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)): - …a cybersecurity policy
## The Steward's obligations Light-touch obligations ([Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)): - …a cybersecurity policy - …cooperate with market surveillance authorities
## The Steward's obligations Light-touch obligations ([Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)): - …a cybersecurity policy - …cooperate with market surveillance authorities - …report actively exploited vulnerabilities and severe incidents (CSIRTs / ENISA)
## The Steward's obligations Light-touch obligations ([Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)): - …a cybersecurity policy - …cooperate with market surveillance authorities - …report actively exploited vulnerabilities and severe incidents (CSIRTs / ENISA) - …single point of contact for authorities, CSIRTs, manufacturers, etc.
## The Steward's obligations Light-touch obligations ([Article 24](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24)): - …a cybersecurity policy - …cooperate with market surveillance authorities - …report actively exploited vulnerabilities and severe incidents (CSIRTs / ENISA) - …single point of contact for authorities, CSIRTs, manufacturers, etc. And the upstream implications!
## A Steward for CPAN is different
## A Steward for CPAN is different - _Tens of thousands_ of projects, with a long tail of transitive dependencies
## A Steward for CPAN is different - _Tens of thousands_ of projects, with a long tail of transitive dependencies - No existing organisation willing and able to be the Steward
## A Steward for CPAN is different - _Tens of thousands_ of projects, with a long tail of transitive dependencies - No existing organisation willing and able to be the Steward - A _laissez-faire_ tradition
## A Steward for CPAN is different - _Tens of thousands_ of projects, with a long tail of transitive dependencies - No existing organisation willing and able to be the Steward - A _laissez-faire_ tradition - A fiercely independent culture
## A Steward for CPAN is different - _Tens of thousands_ of projects, with a long tail of transitive dependencies - No existing organisation willing and able to be the Steward - A _laissez-faire_ tradition - A fiercely independent culture **How do we introduce a Steward to an entire ecosystem _on the community's terms_?**
## Design criteria
## Design criteria - Non-profit, community-owned, democratically governed
## Design criteria - Non-profit, community-owned, democratically governed - Free to join, leave and rejoin
## Design criteria - Non-profit, community-owned, democratically governed - Free to join, leave and rejoin - Minimum obligations – membership is the marker of viability
## Design criteria - Non-profit, community-owned, democratically governed - Free to join, leave and rejoin - Minimum obligations – membership is the marker of viability - Operate as a business – not dependent on donations
## Design criteria - Non-profit, community-owned, democratically governed - Free to join, leave and rejoin - Minimum obligations – membership is the marker of viability - Operate as a business – not dependent on donations - Support the forgotten and "hidden" dependencies
## Design criteria - Non-profit, community-owned, democratically governed - Free to join, leave and rejoin - Minimum obligations – membership is the marker of viability - Operate as a business – not dependent on donations - Support the forgotten and "hidden" dependencies - Everyone remains **fully in control** of their projects
### A **community-owned** non-profit co-operative Owned by those who opt in:
### A **community-owned** non-profit co-operative Owned by those who opt in: - **Project maintainers** – where manufacturers' biggest compliance costs are
### A **community-owned** non-profit co-operative Owned by those who opt in: - **Project maintainers** – where manufacturers' biggest compliance costs are - **Service administrators** – running the infrastructure everyone relies on
### A **community-owned** non-profit co-operative Owned by those who opt in: - **Project maintainers** – where manufacturers' biggest compliance costs are - **Service administrators** – the infrastructure everyone relies on - **Community organisers** – where trust and skills are built
### A community-owned **non-profit** co-operative
### A community-owned **non-profit** co-operative _Dugnad_ – helping your neighbours improve the commons
### A community-owned **non-profit** co-operative _Dugnad_ – helping your neighbours improve the commons Some work is too boring to find volunteers for
### A community-owned **non-profit** co-operative _Dugnad_ – helping your neighbours improve the commons Some work is too boring to find volunteers for - Members are not hired, and get no wage
### A community-owned **non-profit** co-operative _Dugnad_ – helping your neighbours improve the commons Some work is too boring to find volunteers for - Members are not hired, and get no wage - …they are **co-owners receiving donations** – Goal: 20% FTE (one weekday)
### A community-owned **non-profit** co-operative _Dugnad_ – helping your neighbours improve the commons Some work is too boring to find volunteers for - Members are not hired, and get no wage - …they are **co-owners receiving donations** – Goal: 20% FTE (one weekday) - …and any surplus goes to members, non-members, or reinvestment
### A community-owned **non-profit** co-operative _Dugnad_ – helping your neighbours improve the commons Some work is too boring to find volunteers for - Members are not hired, and get no wage - …they are **co-owners receiving donations** – Goal: 20% FTE (one weekday) - …and any surplus goes to members, non-members, or reinvestment The General Assembly decides the disbursement formula
### A community-owned non-profit **co-operative**
### A community-owned non-profit **co-operative** Following the seven [Rochdale Principles](https://en.wikipedia.org/wiki/Rochdale_Principles): - Voluntary and open membership - Democratic member control - Member economic participation - Autonomy and independence - Education, training and information - Co-operation among co-operatives - Concern for community
### A community-owned non-profit **co-operative** Following the seven [Rochdale Principles](https://en.wikipedia.org/wiki/Rochdale_Principles): - Voluntary and open membership - Democratic member control - Member economic participation - Autonomy and independence - Education, training and information - Co-operation among co-operatives - Concern for community Set up as a European Cooperative Society ([Societas cooperativa Europaea (SCE)](https://en.wikipedia.org/wiki/Societas_cooperativa_Europaea))
## Voluntary Security Attestations (VSAs)
## Voluntary Security Attestations (VSAs) A claim **issued by the maintainer**, **signed by the Steward**
## Voluntary Security Attestations (VSAs) A claim **issued by the maintainer**, **signed by the Steward** - …about a project's viability and intended use in products
## Voluntary Security Attestations (VSAs) A claim **issued by the maintainer**, **signed by the Steward** - …about a project's viability and intended use in products - …covering specific releases, valid for a limited time
## Voluntary Security Attestations (VSAs) A claim **issued by the maintainer**, **signed by the Steward** - …about a project's viability and intended use in products - …covering specific releases, valid for a limited time - …and a receipt for the manufacturer's contribution to the project
## Voluntary Security Attestations (VSAs) A claim **issued by the maintainer**, **signed by the Steward** - …about a project's viability and intended use in products - …covering specific releases, valid for a limited time - …and a receipt for the manufacturer's contribution to the project The CRA opens for this ([Recital (21)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_21), [Recital (117)](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_117), [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25)) ⚠️ **No delegated act published yet – this part is speculation**
## How VSAs are issued
## How VSAs are issued 1. Steward announces itself and its signing identity
## How VSAs are issued 1. Steward announces itself and its signing identity 1. Manufacturer finds it depends on a project, and **pays an enrolment fee**
## How VSAs are issued 1. Steward announces itself and its signing identity 1. Manufacturer finds it depends on a project, and **pays an enrolment fee** 1. Maintainer **may choose** to join, and declares the Steward in the project's metadata
## How VSAs are issued 1. Steward announces itself and its signing identity 1. Manufacturer finds it depends on a project, and **pays an enrolment fee** 1. Maintainer **may choose** to join, and declares the Steward in the project's metadata 1. Maintainer attests to compliance and viability
## How VSAs are issued 1. Steward announces itself and its signing identity 1. Manufacturer finds it depends on a project, and **pays an enrolment fee** 1. Maintainer **may choose** to join, and declares the Steward in the project's metadata 1. Maintainer attests to compliance and viability 1. Steward reaffirms and **signs the VSA**, on a recurring schedule
## How VSAs are issued 1. Steward announces itself and its signing identity 1. Manufacturer finds it depends on a project, and **pays an enrolment fee** 1. Maintainer **may choose** to join, and declares the Steward in the project's metadata 1. Maintainer attests to compliance and viability 1. Steward reaffirms and **signs the VSA**, on a recurring schedule 1. Subscribing manufacturers **receive signed VSAs**
## How VSAs are issued 1. Steward announces itself and its signing identity 1. Manufacturer finds it depends on a project, and **pays an enrolment fee** 1. Maintainer **may choose** to join, and declares the Steward in the project's metadata 1. Maintainer attests to compliance and viability 1. Steward reaffirms and **signs the VSA**, on a recurring schedule 1. Subscribing manufacturers **receive signed VSAs** 1. Market surveillance authority audits – and **verifies the VSAs**
## For manufacturers
## For manufacturers Due diligence asks:
## For manufacturers Due diligence asks: - **Intended for commercial use?** – vulnerability handling, responsive maintainers, current metadata
## For manufacturers Due diligence asks: - **Intended for commercial use?** – vulnerability handling, responsive maintainers, current metadata - **Viable and sustained?** – governance, long-term commitments, funding options in use
## For manufacturers Due diligence asks: - **Intended for commercial use?** – vulnerability handling, responsive maintainers, current metadata - **Viable and sustained?** – governance, long-term commitments, funding options in use Signed VSAs answer both – funded by the enrolment fee, sustained by the subscription
## For the community
## For the community Members receive **recurring donations**, per the disbursement formula
## For the community Members receive **recurring donations**, per the disbursement formula At the General Assembly, members: - …propose disbursement formulas - …vote on which one to use - …elect the board
## For the community Members receive **recurring donations**, per the disbursement formula At the General Assembly, members: - …propose disbursement formulas - …vote on which one to use - …elect the board Leaving? Just change the Steward in your project's metadata
## Membership criteria
## Membership criteria - Maintainer, service administrator or community organiser
## Membership criteria - Maintainer, service administrator or community organiser - Non-profit or volunteer basis
## Membership criteria - Maintainer, service administrator or community organiser - Non-profit or volunteer basis - Project in use by a manufacturer, upstream of one, or serving the community
## Membership criteria - Maintainer, service administrator or community organiser - Non-profit or volunteer basis - Project in use by a manufacturer, upstream of one, or serving the community - Meets the "light-touch" Steward obligations
## Membership criteria - Maintainer, service administrator or community organiser - Non-profit or volunteer basis - Project in use by a manufacturer, upstream of one, or serving the community - Meets the "light-touch" Steward obligations - Committed to long-term care, succession and sunset plans
## Membership criteria - Maintainer, service administrator or community organiser - Non-profit or volunteer basis - Project in use by a manufacturer, upstream of one, or serving the community - Meets the "light-touch" Steward obligations - Committed to long-term care, succession and sunset plans - Takes part in issuing VSAs
## Funding model
## Funding model 1. **Public funding** – until established
## Funding model 1. **Public funding** – until established 1. **Enrolment fees** – paid once by manufacturers
## Funding model 1. **Public funding** – until established 1. **Enrolment fees** – paid once by manufacturers 1. **VSA subscriptions** – recurring
## Funding model 1. **Public funding** – until established 1. **Enrolment fees** – paid once by manufacturers 1. **VSA subscriptions** – recurring Goal: **no donations or public funding needed** in the long run
## Next steps
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act - Put together a business case for the co-op
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act - Put together a business case for the co-op - Draft the SCE bylaws – legal, tax and antitrust questions
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act - Put together a business case for the co-op - Draft the SCE bylaws – legal, tax and antitrust questions - Founding members: ≥3 legal entities, in ≥2 EEA countries
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act - Put together a business case for the co-op - Draft the SCE bylaws – legal, tax and antitrust questions - Founding members: ≥3 legal entities, in ≥2 EEA countries - TPRF, Vienna.pm, Mongueurs de Perl, Oslo.pm, & others
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act - Put together a business case for the co-op - Draft the SCE bylaws – legal, tax and antitrust questions - Founding members: ≥3 legal entities, in ≥2 EEA countries - TPRF, Vienna.pm, Mongueurs de Perl, Oslo.pm & others
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act - Put together a business case for the co-op - Draft the SCE bylaws – legal, tax and antitrust questions - Founding members: ≥3 legal entities, in ≥2 EEA countries - TPRF, Vienna.pm, Mongueurs de Perl, Oslo.pm & others - Fundraising for the SCE's starting capital
## Next steps - EU Commission publishes the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) delegated act - Put together a business case for the co-op - Draft the SCE bylaws – legal, tax and antitrust questions - Founding members: ≥3 legal entities, in ≥2 EEA countries - TPRF, Vienna.pm, Mongueurs de Perl, Oslo.pm & others - Fundraising for the SCE's starting capital - A lot of talking!
## So, can we have one?
## So, can we have one? **Yes** – if… - …the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) programme allows attestations to sustain projects
## So, can we have one? **Yes** – if… - …the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) programme allows attestations to sustain projects - …≥3 Perl communities with legal entities join as founders
## So, can we have one? **Yes** – if… - …the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) programme allows attestations to sustain projects - …≥3 Perl communities with legal entities join as founders - …we raise the starting capital
## So, can we have one? **Yes** – if… - …the [Article 25](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25) programme allows attestations to sustain projects - …≥3 Perl communities with legal entities join as founders - …we raise the starting capital - …maintainers choose to opt in
## How you can help
## How you can help - Read the proposal: [The OSS Ecosystem Steward](https://security.metacpan.org/docs/ecosystem-steward.html)
## How you can help - Read the proposal: [The OSS Ecosystem Steward](https://security.metacpan.org/docs/ecosystem-steward.html) - Send comments and concerns in TPRF Slack #cpan-steward channel
## How you can help - Read the proposal: [The OSS Ecosystem Steward](https://security.metacpan.org/docs/ecosystem-steward.html) - Send comments and concerns in TPRF Slack #cpan-steward channel - Does your Perl community have a legal entity? Become a founding member! Note:
# Thanks! Salve J. Nilsen 🐘 Mastodon — @sjn\@chaos.social 🦆🦆 [(EU) Regulation 2024/2847 (Cyber Resilience Act)]:https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:L_202402847 '(EU) Regulation 2024/2847 (Cyber Resilience Act)' [Regulation (EU) 2019/881, Article (48)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32019R0881#art_48 'Request for a European cybersecurity certification scheme' [EU Blue Guide]:https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.C_.2022.247.01.0001.01.ENG&toc=OJ%3AC%3A2022%3A247%3ATOC 'The Blue Guide on the implementation of EU product rules (2022/C 247/01)' [CC-BY-SA-4.0]:https://creativecommons.org/licenses/by-sa/4.0/deed 'Creative Commons Attrubution Sharealike 4.0 License' [CISA-2023-4]:https://www.cisa.gov/resources-tools/resources/types-software-bill-materials-sbom 'CISA Types of Software Bill of Materials (SBOM)' [CISA-2024-10]:https://www.cisa.gov/sites/default/files/2024-10/SBOM%20Framing%20Software%20Component%20Transparency%202024.pdf 'CISA Framing Software Component Transparency: Establishing a Common Software Bill of Materials (SBOM)' [CSCRF]:https://www.sebi.gov.in/legal/circulars/aug-2024/cybersecurity-and-cyber-resilience-framework-cscrf-for-sebi-regulated-entities-res-_85964.html 'Cybersecurity and Cyber Resilience Framework (CSCRF) for SEBI Regulated Entities (REs)' [TR-03183]:https://bsi.bund.de/dok/TR-03183 'TR-03183 Cyber Resilience Requirements for Manufacturers and Products, Part 2' [NTIA-SBOM]:https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf#page=9 'NTIA Minimum Elements for a Software Bill of Materials (SBOM)' [CRA FAQ]:https://digital-strategy.ec.europa.eu/en/library/cyber-resilience-act-implementation-frequently-asked-questions 'FAQs on the CRA implementation' [CRA FAQ - linkable copy]:https://cra.orcwg.org/faq/official/ 'Linkable version of the Official CRA FAQ by the Open Regulatory Compliance Working Group (ORCWG)' [CRA FAQ 1.1.2]:https://cra.orcwg.org/faq/official/faq_1-1-2/ "What is a product with digital elements? Are stand-alone software or firmware products with digital elements?" [CRA FAQ 4.1.1]:https://cra.orcwg.org/faq/official/faq_4-1-1/ "What does the CRA require of the manufacturer's cybersecurity risk assessment?" [CRA FAQ 4.3.6]:https://cra.orcwg.org/faq/official/faq_4-3-6/ 'How should vulnerabilities in integrated components be addressed and remedied?' [CRA Guidance]:https://digital-strategy.ec.europa.eu/en/library/commission-publishes-new-guidance-support-timely-cyber-resilience-act-implementation 'Commission guidance on the application of the Cyber Resilience Act (CRA)' [CRA Guidance chapter 2]:https://cra.orcwg.org/official-guidance/#sct_2 'CRA Guidance Chapter 2: Scope' [CRA Guidance chapter 3]:https://cra.orcwg.org/official-guidance/#sct_3 'CRA Guidance Chapter 3: Free and open-source software' [CRA Guidance section 3.3]:https://cra.orcwg.org/official-guidance/#sct_3.sct_3 'CRA Guidance Section 3.3: Open-source software stewards' [ORCWG]:https://orcwg.org/ [ORCWG FAQ]:https://cra.orcwg.org/ [ORCWG copy of the official CRA FAQ]:https://cra.orcwg.org/faq/ [ORCWG copy of the official CRA Guidance]:https://cra.orcwg.org/faq/ [Hobson's Choice]:https://en.wikipedia.org/wiki/Hobson%27s_choice "A Hobson's choice is a free choice in which only one thing is actually offered. The term is often used to describe an illusion that choices are available. The best known example is «I'll give you a choice: take it or leave it», wherein «leaving it» is strongly undesirable." [Societas cooperativa Europaea (SCE)]:https://en.wikipedia.org/wiki/Societas_cooperativa_Europaea 'A special cooperative entity, that may be set up and operate throughout the European Economic Area, allowing them to move their headquarters freely from one member state to another.' [Rochdale Principles]:https://en.wikipedia.org/wiki/Rochdale_Principles 'The Rochdale Principles, also known as the seven co-operative principles.' [Recital (1)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_1 'Two major problems adding costs for users and society should be addressed' [Recital (10)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_10 'CRA relevance for supply chains' [Recital (15)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_15 'CRA applies to economic operators that have an intention to monetise a product' [Recital (18)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_18 'Open Source Software Contributors' [Recital (19)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_19 'Open Source Software Stewards, light-touch regulatory regime, and CE mark implications' [Recital (20)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_20 'Open Source package managers considerations as "distributors"' [Recital (21)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_21 'Voluntary security attestation programs for Open Source projects' [Recital (22)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_22 'Submission of SBOMs for Open Source projects' [Recital (24)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_24 'CRA relevance for the NIS2 directive' [Recital (31)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_31 "Manufacturer's liability due to lack of security updates" [Recital (34)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_34 'Exercise due diligence when integrating third-party components' [Recital (37)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_37 'Software for testing purposes, alphas, betas' [Recital (39)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_39 'Continued security updates' [Recital (41)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_41 'Substantial modifications requires a new conformity assessment to be done' [Recital (43)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_43 'Important products with digital elements' [Recital (44)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_44 'Class I and Class II products' [Recital (45)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_45 'Class II products are subject to mandatory third-party conformity assessment' [Recital (56)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_56 'On the download and installation of security updates, and notification of end of support' [Recital (57)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_57 'On the requirement to be able to get security updates separately from functionality updates' [Recital (60)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_60 'Support period' [Recital (61)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_61 'Support period' [Recital (62)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_62 'Support period' [Recital (63)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_63 'Point of contact' [Recital (64)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_64 'Secure by default' [Recital (65)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_65 'Notify of severe incidents or actively exploited vulnerabilities' [Recital (77)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_77 'Manufacturers should facilitate vulnerability analysis by drawing up an SBOM, though they are not obliged to make it public' [Recital (117)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#rct_117 '[…] establish voluntary security attestation programmes for assessing the conformity of products with digital elements qualifying as free and open-source software […]' [Chapter I]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#cpt_I 'General Provisions' [Article 1]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_1 'Subject matter' [Article 2]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_2 'Scope' [Article 3]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_3 'Definitions' [Article 7]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_7 'Important products' [Article 8]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_8 'Critical products' [Article 9]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_9 'Obligations of Manufacturers' [Article 9(1)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_9.tit_1 'Stakeholder consultation' [Chapter II]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#cpt_II 'Obligations of Economic Operators and Provisions in relation to Free and Open-Source Software' [Article 13]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_13 'Obligations of Manufacturers' [Article 13(1)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.001 'Manufacturers shall ensure products are developed in accordance with essential cybersecurity requirements' [Article 13(2)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.002 'Manufacturers shall undertake a cybersecurity risk assessment' [Article 13(5)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.005 'Manufacturers shall exercise due diligence when integrating components, including FOSS' [Article 13(6)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.006 'Manufacturers shall share relevant code or documentation with the supplier or maintainer of the component' [Article 13(8)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.008 'Manufacturers shall ensure vulnerabilities are handled for 5 years' [Article 13(9)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.009 'Manufacturers shall keep security updates available for 10 years after they are issued, or for the rest of the support period, whichever is longer' [Article 13(12)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.012 'Manufacturers shall before placing a product on the market, draw up technical documentation' [Article 13(14)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.014 'Manufacturers shall ensure that procedures are in place for products to remain in conformity with this Regulation' [Article 13(15)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.015 'Manufacturers shall ensure that their products is identifiable' [Article 13(16)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.016 'Manufacturers shall indicate their name and identification' [Article 13(17)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.017 'Manufacturers shall designate a single point of contact for reporting vulnerabilities' [Article 13(18)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.018 'Manufacturers shall ensure products are accompanied by documentation listed in Annex II, and available for at least 10 years' [Article 13(19)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.019 'Manufacturers shall shall clearly mark the end date of the support period' [Article 13(20)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#013.020 'Manufacturers shall provide a copy of or the exact internet addrees to the EU declaration of conformity' [Article 14]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_14 'Reporting obligations of manufacturers' [Article 14(1)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#014.001 'A manufacturer shall notify any actively exploited vulnerability contained in the product that it becomes aware of' [Article 14(2)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#014.002 'A manufacturer shall notify within 24 hours, 72 hours and 14 days' [Article 14(3)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#014.003 'A manufacturer shall notify any severe incident having an impact on the security of the product that it becomes aware of' [Article 14(8)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#014.008 'After becoming aware of an incident or vulnerability, the manufacturer shall inform the impacted users of the product, and about risk mitigation and any corrective measures that users can deploy' [Article 15]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_15 'Voluntary reporting' [Article 16]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_16 'Establishment of a single reporting platform' [Article 17]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_17 'Other provisions related to reporting' [Article 18]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_18 'Authorised representatives' [Article 19]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_19 'Obligations of importers' [Article 19(1)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#019.001 'Importers shall only place products on the market that comply with requirements in Annex I part I' [Article 20]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_20 'Obligations of distributors' [Article 21]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_21 'Cases in which obligations of manufacturers apply to importers and distributors' [Article 22]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_22 'Other cases in which obligations of manufacturers apply' [Article 23]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_23 'Identification of economic operators' [Article 23(2)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#023.002 'Be able to present supplier information for 10 years' [Article 24]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_24 'Obligations of open-source software stewards' [Article 24(2)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#024.002 'Open-source software stewards' [Article 25]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_25 'Security attestations of free and open-source software, for conformity assessment' [Article 26]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_26 'Guidance' [Chapter III]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#cpt_III 'Conformity of the product with digital elements' [Article 27]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_27 'Presumption of conformity' [Article 28]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_28 'EU declaration of conformity' [Article 28(1)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#028.001 'Manufacturer states that cybersecurity requirements in [Annex I] has been demonstrated' [Article 28(4)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#028.004 'Manufacturer assumes responsibility for compliance' [Article 29]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_29 'General principles of the CE marking' [Article 30]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_30 'Rules and conditions for affixing the CE marking' [Article 30(3)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#030.003 'The CE marking shall be affixed before the product with digital elements is placed on the market' [Article 32]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_32 'Conformity assessment procedures' [Chapter IV]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#cpt_IV 'Notification of Conformity Assessment Bodies' [Article 47]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_47 'Operational obligations of notified bodies' [Chapter V]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#cpt_V 'Market Surveillance and Enforcement' [Article 52]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_52 'Market surveillance and control of products' [Article 52(3)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#052.003 'Market surveillance authorities shall also be responsible for carrying out market surveillance activities in relation to the obligations for open-source software stewards.' [Article 52(11)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#052.011 'Market surveillance authorities shall inform consumers of where to submit complaints that could indicate non-compliance with this Regulation and facilitate reporting of vulnerabilities, incidents and cyber threats' [Article 54]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_54 'Procedure concerning products presenting a significant cybersecurity risk' [Article 54(1)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#054.001 '[If a market authority finds] sufficient reason to consider that a product, including its vulnerability handling, presents a significant cybersecurity risk, it shall carry out an evaluation of the product concerned in respect of its compliance with all the requirements laid down in this Regulation.' [Article 54(5)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#054.005 '[If the economic operator does] not take adequate corrective action, the market surveillance authority shall take all appropriate provisional measures to prohibit or restrict that product from being made available, to withdraw it from that market or to recall it.' [Article 58]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_58 'Formal non-compliance' [Chapter VII]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#cpt_VII 'Confidentiality and Penalties' [Article 64]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_64 'Penalties' [Article 64(4)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#064.004 'Supplying incorrect, incomplete or misleading information may be fined up to 5M EUR or 1% of global turnover' [Article 64(10)(b)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#064.010 'Rules on administrative fines shall not apply to Open Source Software Stewards' [Chapter VIII]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#cpt_VIII 'Transitional and final provisions' [Article 69]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_69 'Transitional provisions' [Article 69(2)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#069.002 'Products placed on the market before 11 December 2027 shall be subject to this Regulation only if, from that date, those products are subject to a substantial modification.' [Article 69(3)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#069.003 'Obligations laid down in Article 14 shall apply to all products that fall within the scope of this Regulation that have been placed on the market before 11 December 2027.' [Article 71]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#art_71 'Entry into force and application' [Article 71(2)]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#071.002 'This Regulation shall apply from 11 December 2027. However, Article 14 shall apply from 11 September 2026 and Chapter IV (Articles 35 to 51) shall apply from 11 June 2026.' [Annex I]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#anx_I 'Essential Cybersecurity Requirements' [Annex I, Part I]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#d1e47-68-1 'Cybersecurity requirements relating to the properties of products with digital elements' [Annex I, Part II]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#d1e143-68-1 'Vulnerability handling requirements' [Annex II]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#anx_II 'Information and Instructions to the User' [Annex III]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#anx_III 'Important products' [Annex IV]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#anx_IV 'Critical products' [Annex V]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#anx_V 'EU Declaration of Conformity' [Annex VII]:https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847#anx_VII 'Content of the Technical Documentation'