-
Notifications
You must be signed in to change notification settings - Fork 839
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 #41
Comments
Thank you very much. Please send the question to email tianshiyeben@qq.com |
@tianshiyeben - we actually sent an e-mail to you about 1 hour ago to the mentioned e-mail address. Did you receive this? Just for reference, you can find the report here. It is private and only accessible to you 👍 Let me know if you have any questions. |
Thank you very much. I have received it. I will think about how to deal with this problem |
@tianshiyeben - great! Please take your time, and feel free to ask @hi-unc1e for support in the thread 👍 |
ok ok tks @hi-unc1e |
Thank you very much for your suggestions. I already know how to fix it and have started to make some updates |
Hey there!
I belong to an open source security research community, and a member (@hi-unc1e) 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: