-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Trying to get in touch regarding a security issue #2063
Comments
Would you like to come take a look at it, @jc21? Your prompt attention would be appreciated. :) |
Any update on this? I would also like to report something and would appreciate an email or way to privately contact the developers. |
^ Nope. Committed |
How is it that something important like this goes unanswered for almost seven months while commits take place in between? |
Has this been rectified? |
AFAIK, nope. |
Any news on this one? Did @jc21 get in contact with you guys? |
No. |
This is the issue, the advisory is out now: |
@BrutalCoding yes, IMHO this issue should be closed. |
Issue is now considered stale. If you want to keep it open, please comment 👍 |
Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@dwisiswant0) has found a potential issue, which I would be eager to share with you.
Could you add a
SECURITY.md
file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.Looking forward to hearing from you 👍
(cc @huntr-helper)
The text was updated successfully, but these errors were encountered: