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

Create a Security Policy #1302

Closed
wants to merge 2 commits into from
Closed

Create a Security Policy #1302

wants to merge 2 commits into from

Conversation

joycebrum
Copy link

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:

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

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.

@joycebrum
Copy link
Author

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.

@joycebrum
Copy link
Author

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.

@calderjo calderjo closed this Aug 23, 2024
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.

Create a Security Policy
2 participants