loopbackio / loopbackio/security
Formalise Vulnerability Response Process
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
There's no documentation on the how we handle and respond to vulnerability reports.
This issue is to track creating formal documentation that clearly states end-to-end how a vulnerability report is to be handled.
References
OSSF's OSS Vulnerability Guide: https://github.com/ossf/oss-vulnerability-guide/blob/main/guide.md
Contributor guide
No contributing guide indexed for this repository
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 referenced OSSF OSS Vulnerability Guide and inspecting this repository for any existing security-process material. Define the end-to-end handling and response steps described by the issue, then document the agreed process in the repository. Done means the vulnerability-report workflow is formally documented from receipt through resolution.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100