Create a Security Policy #1302
Closed
Create a Security Policy #1302
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It is also possible to create the SECURITY.md on https://github.com/Kaggle/.github and it will be available to all Kaggle projects (useful if the vulnerability process is the same for all of them), though I am not able to open PRs there since it is empty. |
|
Hi, I noticed the suggestion is quite idle, are you planning on reviewing it? Otherwise I can close it as not planned, just let me know. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #1301
I've created the SECURITY.md file considering the report vulnerability through security advisory, which is a new GitHub feature.
If you're interested in GitHub's feature, it must be activated for the repository:
If you rather not enable it, there is also the possibility to receive the vulnerability report through an email or even using the bug hunter project (since it is a google project). In this case just let me know.
Besides that, feel free to edit or suggest any changes to this document. It is supposed to reflect the amount of effort you can offer to handle vulnerabilities.