Add vulnerability response policy template
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- ruby
- Domain
- documentation, security
Research direction
No file, format, or entry point is named in the issue. First inspect the repository to determine where a vulnerability response policy template belongs and how it should be presented; done means adding a basic reusable template that gems can adapt and publish.
Written by the indexing model from the issue text.
Description
Most gems don't have any set process/policy for handling security vulnerabilities. We should provide a basic template for them to use to make it easier for them to draft one and get it published.
- Dominant language
- HTML
- Stars
- 26
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
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.
More from rubysec/rubysec.github.io
-
documentation enhancement
rubysec/rubysec.github.io#8 · 1 comment · 1 assignee ·
-
documentation enhancement
rubysec/rubysec.github.io#7 · 15 comments · 1 assignee ·
All issues in rubysec/rubysec.github.io
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100