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

Closed
diogoteles08 opened this issue Apr 25, 2023 · 1 comment · Fixed by #810
Closed

Add a Security-Policy #809

diogoteles08 opened this issue Apr 25, 2023 · 1 comment · Fixed by #810

Comments

@diogoteles08
Copy link
Contributor

Hi @klauspost! I'm Diogo and I'm back (see #764) hoping to offer a bit more help with security enhancements.

This time I'm here to suggest that you expose a way that users can report eventual vulnerabilities in a safe and efficient way. This is usually done through a Security Policy, which is a GitHub standard document (SECURITY.md) added on the root of the repo and will be visible to the users in the "Security Tab".

image

It is a recommendation from Github itself, and from Scorecard (being a security measure of medium priority).

Aiming to make this change easier, I'll take the liberty of submitting one suggestion of a Security Policy as a PR. Please feel free to edit it directly or ask me for editions until it is in compliance with how klaupost/compress would best handle vulnerability reports.

@klauspost
Copy link
Owner

Good idea. Added a bit more, specific to the packages here.

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.

3 participants
@klauspost @diogoteles08 and others