-
Notifications
You must be signed in to change notification settings - Fork 30
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 #13
Comments
@JamieSlome you should do full disclosure, the time has passed |
@psmoros (cc) |
Last commit was 5 years ago, I doubt someone will reply. |
I can't find Nick's email anywhere... If you find it feel free to privately reach out otherwise you can just as well open a public issue |
I would really say go full disclosure, ethjs-util is used all over the ecosystem - and keeping the vuln closed endangers users |
Agreed! Sorry I thought you were the original author of the report. We will triage it internally and take a decision soon :) |
* devDeps: webpack@2->3 * npm dedupe; npm audit fix * update dist
Hey there!
I'd like to report a security issue but cannot find contact instructions on your repository.
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: