Skip to content

Who to contact for security issues #3362

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

Closed
JamieSlome opened this issue Jan 17, 2022 · 5 comments
Closed

Who to contact for security issues #3362

JamieSlome opened this issue Jan 17, 2022 · 5 comments

Comments

@JamieSlome
Copy link

Hey there!

I belong to an open source security research community, and a member (@yetingli) 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)

@HackbrettXXX
Copy link
Collaborator

Please contact me under [email protected]. I'm adding a SECURITY.md file in #3364. Thanks for the pointer ;)

@JamieSlome
Copy link
Author

@HackbrettXXX - thanks for the response. We will send an e-mail over shortly! ❤️

@JamieSlome
Copy link
Author

Just for reference, you can view the report here in the meantime:

https://huntr.dev/bounties/30a0b9bd-b3fc-4082-9e67-b563fbbbf0d7/

It is private and only accessible to maintainers with repository write permissions 👍

@github-actions
Copy link

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.

@JamieSlome
Copy link
Author

I think this can be closed as the report has been addressed 👍

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

No branches or pull requests

2 participants