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 Security Policy #621

Merged
merged 1 commit into from
Feb 21, 2024
Merged

Add Security Policy #621

merged 1 commit into from
Feb 21, 2024

Conversation

gabibguti
Copy link
Contributor

Resolves #620

Here's a Security Policy suggestion.

The link for reporting vulnerabilities uses GitHub's Security Advisories report vulnerability feature, which is in beta. You would need to enable the feature in the repo for it to work.

How to enable private vulnerability reports
  1. Open the repo's settings
  2. Click on Code security & analysis
  3. Click "Enable" for "Private vulnerability reporting (Beta)"

I've tried to keep the timelines for confirming vulnerability reports and fixing vulnerabilities as open as possible.

Let me know what do you think and if this seems reasonable for maintenance.

Signed-off-by: Gabriela Gutierrez <gabigutierrez@google.com>
@edschofield edschofield merged commit 0598d1b into PythonCharmers:master Feb 21, 2024
@edschofield
Copy link
Contributor

Thanks Gabriela!

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.

Add Security Policy
2 participants