Instructions for how to report a security vulnerability
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
No file or test is named; start by reviewing the site's existing documentation structure and decide where a vulnerability-reporting page belongs. Done means documenting when to use a public GitHub issue and how to privately report a dangerous exploit before disclosure.
Written by the indexing model from the issue text.
Description
Despite our best efforts, it's likely that a security vulnerability will be discovered by a non-contributor out in the wild. It would be good to have a page instructing them how to best report the issue so that it can be resolved. I imagine that a lot of security issues can be reported as basic GitHub issues, but I believe we need to allow for the possibility of an exploit that is so dangerous that it would be better not to publish it until after we have a fix in place.
- Dominant language
- MDX
- Stars
- 187
- Forks
- 317
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 blitz-js/blitzjs.com
-
invalid route/link in docs/rpc-setupPossibly taken @justinbalaguer claimed this 712 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 45/100
blitz-js/blitzjs.com#866 ·
-
status/triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
blitz-js/blitzjs.com#850 ·
-
status/triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
blitz-js/blitzjs.com#849 · 1 comment ·
-
status/ready-to-work-on
Difficulty 3/5 1-2 days Newbie friendliness 25/100
blitz-js/blitzjs.com#856 · 2 comments ·
-
status/triage
Difficulty 1/5 Under an hour Newbie friendliness 50/100
blitz-js/blitzjs.com#836 ·
All issues in blitz-js/blitzjs.com
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
IngvarConsulting/unica#2006 ·
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
DepressionCenter/agentprise#51 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
sergey-miryanov/gcmon#230 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
KhronosGroup/Vulkan-Guide#397 · 2 comments ·