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

Closed
diogoteles08 opened this issue Jun 19, 2023 · 0 comments · Fixed by #156
Closed

Add a Security-Policy #155

diogoteles08 opened this issue Jun 19, 2023 · 0 comments · Fixed by #156

Comments

@diogoteles08
Copy link
Contributor

Hi! I'm Diogo and I'm back (see #140) 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 that will be visible to the users in the "Security Tab", as you can see bellow:

image

Having a Security Policy 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 and submit a 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 mvdnes/spin-rs would best handle vulnerability reports.

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