Skip to content

Conversation

@shettyvarshaa
Copy link
Contributor

@shettyvarshaa shettyvarshaa commented Oct 25, 2023

Created a Security Policy to enhance community profile of the repository and to prevent potential vulnerabilities

What does this PR do?

Fixes #24627

Before submitting

  • This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
  • Did you read the contributor guideline,
    Pull Request section?
  • Was this discussed/approved via a Github issue or the forum? Please add a link
    to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the
    documentation guidelines, and
    here are tips on formatting docstrings.
  • Did you write any new necessary tests?

Issue raised in the forum

Who can review?

CC : @stevhliu

Created a Security Policy to enhance community profile of the repository and to prevent potential vulnerabilities
Copy link
Member

@stevhliu stevhliu left a comment

Choose a reason for hiding this comment

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

Instead of creating a new security doc (the first section looks like its copied from CONTRIBUTING.MD), I think we can just add a Security section in CONTRIBUTING.MD.

WDYT @ArthurZucker?

@shettyvarshaa
Copy link
Contributor Author

shettyvarshaa commented Oct 25, 2023

Yes, I thought of adding handling bug into security policy which is also mentioned in contributing.md, but also, creating security doc will complete your community profile to meet the standards defined for a Repo

Screenshot of this repo's current community profile

@ArthurZucker
Copy link
Collaborator

No strong opinion, but will ask internally to have guidance regarding the bounty hunting program rather than bug fixed in this!

@ArthurZucker
Copy link
Collaborator

15cd096 fixes this 😉 thanks for the tip 🤗

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.

3 participants