-
Notifications
You must be signed in to change notification settings - Fork 22.9k
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
Add a Security-Policy #3691
Comments
Good point. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! I'm Diogo and I'm back (see #3636) hoping to offer a bit more help with security enhancements.
This time I'm here to suggest that you expose a way that users can report eventual vulnerabilities in a safe and efficient way. This is usually done through a Security Policy, which is a GitHub standard document (SECURITY.md) added on the root of the repo and that will be visible to the users in the "Security Tab", as you can see bellow:
Having a Security Policy is a recommendation from Github itself, and from Scorecard (being a security measure of medium priority).
Aiming to make this change easier, I'll take the liberty and submit a suggestion of a Security Policy as a PR. Please feel free to edit it directly or ask me for editions until it is in compliance with how d3/d3 would best handle vulnerability reports.
The text was updated successfully, but these errors were encountered: