Cyber Resilience Act readiness
Open
Nobody has claimed this yet.
documentation
outreach
security
- Dominant language
- No language data
- Stars
- 12
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Establish what the EU Cyber Resilience Act means for Wagtail, as an upstream project in the open source software supply chain, and related security improvements that could be considered.
Intended outcome
For now the focus will be on improvements that are generally valuable for a wide range cybersecurity requirements, such as:
- Revising our security policies and docs, in particular with more information on our behind-the-scenes security team process.
- Producing SBOMs for our releases, and signing release artifacts.
- Signposting and sharing how to do this as part of the package ecosystem, via changes to our package guidelines.
More information
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked security policies and docs, the package guidelines, and issues #14293 and #14287. Define the Cyber Resilience Act implications for Wagtail and agree on scoped improvements for security processes, SBOMs, release signing, and package-ecosystem guidance; done means an agreed readiness plan.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100