-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
chore(security): upgrade reporting policy #8083
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Aviv Keller <me@aviv.sh>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the Node.js Security Reporting documentation to reflect the latest security policies and procedures from the main Node.js repository. The changes improve clarity, update timelines, and modernize the content structure.
- Updated acknowledgment timelines and added context about holiday delays
- Refined the security disclosure process description for better clarity
- Simplified references and improved formatting consistency
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
cc @nodejs/security-wg |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Aviv Keller <me@aviv.sh>
bjohansebas
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, shouldn’t the security group be the codeowner of this page?
|
Lighthouse Results
|
This PR updates our Security Reporting page with the latest information on https://github.com/nodejs/node/security/policy.