-
Notifications
You must be signed in to change notification settings - Fork 187
Update email to report the security vulnerabilities #803
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
CC @jupyter/security |
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.
Thank you @krassowski!
@krassowski could we make this a stronger statement and say that we prefer the GitHub-based workflow and treat the email as a fallback? Or is that too much? |
Nvm I missed that it was there! |
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.
A few small language changes but LGTM! I'll commit them and merge. Thanks @krassowski for the follow-up!
Thank you! |
Also mention that private vulnerability reports via GHSA are the preferred approach.
References: