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 #819

Merged
merged 1 commit into from
Apr 11, 2023
Merged

Add Security Policy #819

merged 1 commit into from
Apr 11, 2023

Conversation

gabibguti
Copy link
Contributor

Description
Resolves #818

This is a Security Policy suggestion.

The link for reporting vulnerabilities uses the security advisory, which is a GitHub feature that is in beta. You would need to enable the feature in the repo for it to work.

How to enable Security Advisory
  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 of confirming a vulnerability report and fixing a vulnerability as open as possible. Let me know what you think and if this seems reasonable for maintenance.

Checklist

  • The documentation has been updated.
  • If the PR solves a specific issue, it is set to be closed on merge.

Signed-off-by: Gabriela Gutierrez <gabigutierrez@google.com>
Copy link
Collaborator

@weslleyspereira weslleyspereira left a comment

Choose a reason for hiding this comment

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

Looks good to me. Thanks!!

@langou langou merged commit 647dded into Reference-LAPACK:master Apr 11, 2023
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
3 participants