Skip to content
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 #3343

Closed
pnacht opened this issue Apr 25, 2023 · 0 comments · Fixed by #3344
Closed

Add a security policy #3343

pnacht opened this issue Apr 25, 2023 · 0 comments · Fixed by #3344

Comments

@pnacht
Copy link
Contributor

pnacht commented Apr 25, 2023

Hey, it's Pedro and I'm back (see #3319) with another security suggestion!

This time I'd like to suggest that seaborn publish a security policy. A security policy (SECURITY.md) explains how the project wishes to receive and handle responsible disclosure of potential vulnerabilities. GitHub recommends that projects have one.

The security policy can be found by users who enter the project's "Security" panel. They'll also see references to it in the "New issue" page.

There are two main ways to receive disclosures:

If you want to use GitHub's reporting system, it must be activated for the repository:

  1. Open the repo's settings
  2. Click on Code security & analysis
  3. Click "Enable" for "Private vulnerability reporting"

I'll send a PR with a draft policy along with this issue.

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 a pull request may close this issue.

1 participant