spinframework / spinframework/spin
Create a runbook for handling security disclosures
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
Relevant CNCF hygiene reading: https://contribute.cncf.io/projects/best-practices/security/security-hygiene/
Inspiration: https://docs.wasmtime.dev/security-vulnerability-runbook.html
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 CNCF security-hygiene guidance and the Wasmtime security vulnerability runbook for structure and expected coverage. Document Spin's security-disclosure handling process in a project runbook, with enough detail for maintainers to follow it consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100