Skip to content

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

Merged
merged 2 commits into from
Jun 13, 2025

Conversation

krassowski
Copy link
Member

@krassowski krassowski commented Jun 12, 2025

Also mention that private vulnerability reports via GHSA are the preferred approach.

References:

@krassowski
Copy link
Member Author

CC @jupyter/security

@krassowski krassowski marked this pull request as ready for review June 13, 2025 09:31
Copy link
Member

@consideRatio consideRatio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you @krassowski!

@choldgraf
Copy link
Collaborator

@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?

@choldgraf
Copy link
Collaborator

Nvm I missed that it was there!

Copy link
Collaborator

@choldgraf choldgraf left a 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!

@choldgraf choldgraf merged commit e6b21c9 into jupyter:main Jun 13, 2025
1 of 2 checks passed
@krassowski
Copy link
Member Author

Thank you!

@krassowski krassowski deleted the update-security-reporting branch June 13, 2025 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants