-
Notifications
You must be signed in to change notification settings - Fork 102
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
Who to contact for security issues #122
Comments
@JamieSlome thanks for taking the time to open this issue! A SECURITY.md file has been created. |
@lquixada - thanks for creating the We will get further details sent over to the elected e-mail address shortly. In the meantime, the report can be accessed directly here: It is private and only accessible to you @lquixada 👍 |
thanks @JamieSlome ! will take a look! |
@lquixada - great, on call if you need me for any support, plus @ranjit-git for any questions regarding the report 😃 |
Hey there!
I belong to an open source security research community, and a member (@ranjit-git) has found an issue, but doesn’t know the best way to disclose it.
If not a hassle, might you kindly add a
SECURITY.md
file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)
The text was updated successfully, but these errors were encountered: