comment: # (…or by running the Makefile with “make”)
comment: # (mdslides can be installed from https://github.com/dadoomer/markdown-slides/)
comment: # (width: “1440”)
comment: # (height: “810”)
comment: # (help: true)
comment: # (progress: true)
comment: # (controlsBackArrows: true)
comment: # (center: false)
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
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
- A community co-op, owned by the people who look after our core projects, services and communities.
The concept, in three sentences
- A community co-op, owned by the people who look after our core projects, services and communities.
- Companies buy attestations from maintainers, to help them be secure & compliant – and that money sustains the community.
The concept, in three sentences
- A community co-op, owned by the people who look after our core projects, services and communities.
- Companies buy attestations from maintainers, to help them be secure & compliant – and that money sustains the community.
- 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)
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
Upstream implications
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))
Upstream implications
- Support period matching expected use, e.g. 5 years (Article 13(8))
Open Source components used in the product, or in its remote data processing solutions, should be supported for the same period.
Upstream implications
Upstream implications
Software update services that depend on Open Source need to stay secure and available for the same period.
Upstream implications
Upstream implications
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))
Upstream implications
- Fixes shared with upstream – someone has to receive them (Article 13(6))
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
Accept – demonstrate the project is intended for commercial use
Accept – demonstrate the project is intended for commercial use
…and take on boring, tedious compliance work
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
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
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, Article 24)
- …a legal entity, but not a person or manufacturer
The Open Source Software Steward
A new legal category in the CRA (Article 3, Article 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, Article 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, Article 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):
The Steward’s obligations
Light-touch obligations (Article 24):
- …a cybersecurity policy
- …cooperate with market surveillance authorities
The Steward’s obligations
Light-touch obligations (Article 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):
- …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):
- …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
Owned by those who opt in:
Owned by those who opt in:
- Project maintainers – where manufacturers’ biggest compliance costs are
Owned by those who opt in:
- Project maintainers – where manufacturers’ biggest compliance costs are
- Service administrators – running the infrastructure everyone relies on
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
Dugnad – helping your neighbours improve the commons
Dugnad – helping your neighbours improve the commons
Some work is too boring to find volunteers for
Dugnad – helping your neighbours improve the commons
Some work is too boring to find volunteers for
- Members are not hired, and get no wage
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)
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
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
Following the seven 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
Following the seven 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))
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), Recital (117), Article 25)
⚠️ No delegated act published yet – this part is speculation
How VSAs are issued
How VSAs are issued
- Steward announces itself and its signing identity
How VSAs are issued
- Steward announces itself and its signing identity
- Manufacturer finds it depends on a project, and pays an enrolment fee
How VSAs are issued
- Steward announces itself and its signing identity
- Manufacturer finds it depends on a project, and pays an enrolment fee
- Maintainer may choose to join, and declares the Steward in the project’s metadata
How VSAs are issued
- Steward announces itself and its signing identity
- Manufacturer finds it depends on a project, and pays an enrolment fee
- Maintainer may choose to join, and declares the Steward in the project’s metadata
- Maintainer attests to compliance and viability
How VSAs are issued
- Steward announces itself and its signing identity
- Manufacturer finds it depends on a project, and pays an enrolment fee
- Maintainer may choose to join, and declares the Steward in the project’s metadata
- Maintainer attests to compliance and viability
- Steward reaffirms and signs the VSA, on a recurring schedule
How VSAs are issued
- Steward announces itself and its signing identity
- Manufacturer finds it depends on a project, and pays an enrolment fee
- Maintainer may choose to join, and declares the Steward in the project’s metadata
- Maintainer attests to compliance and viability
- Steward reaffirms and signs the VSA, on a recurring schedule
- Subscribing manufacturers receive signed VSAs
How VSAs are issued
- Steward announces itself and its signing identity
- Manufacturer finds it depends on a project, and pays an enrolment fee
- Maintainer may choose to join, and declares the Steward in the project’s metadata
- Maintainer attests to compliance and viability
- Steward reaffirms and signs the VSA, on a recurring schedule
- Subscribing manufacturers receive signed VSAs
- 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
Members receive recurring donations, per the disbursement formula
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
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
- Public funding – until established
Funding model
- Public funding – until established
- Enrolment fees – paid once by manufacturers
Funding model
- Public funding – until established
- Enrolment fees – paid once by manufacturers
- VSA subscriptions – recurring
Funding model
- Public funding – until established
- Enrolment fees – paid once by manufacturers
- VSA subscriptions – recurring
Goal: no donations or public funding needed in the long run
Next steps
Next steps
- EU Commission publishes the Article 25 delegated act
Next steps
- EU Commission publishes the Article 25 delegated act
- Put together a business case for the co-op
Next steps
- EU Commission publishes the Article 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 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 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 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 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 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 programme allows attestations to sustain projects
So, can we have one?
Yes – if…
- …the Article 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 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 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
How you can help
How you can help
- Read the proposal: The OSS Ecosystem Steward
- 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
🦆🦆