Skip to content
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 #2023

Closed
JamieSlome opened this issue Jan 12, 2022 · 8 comments
Closed

Trying to get in touch regarding a security issue #2023

JamieSlome opened this issue Jan 12, 2022 · 8 comments

Comments

@JamieSlome
Copy link
Contributor

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)

@DABH
Copy link
Contributor

DABH commented Jan 12, 2022

Email me at npm view yadeep maintainers.email. Thanks!

PR welcome for adding a SECURITY.md

@JamieSlome
Copy link
Contributor Author

@DABH - thanks for your follow-up!

Just for reference, the report can be found here:

https://huntr.dev/bounties/de65cf7d-675a-4515-b731-81fda23cd5e7/

It is private and only accessible to maintainers with repository write permissions. Let me know if you have any further questions!

@JamieSlome
Copy link
Contributor Author

Also created PR:

#2024

@DABH DABH closed this as completed Jan 13, 2022
@wbt
Copy link
Contributor

wbt commented Jan 13, 2022

I believe the above should be interpreted as reporting the issue that this repository lacked a way to get in touch about security issues, and that's been resolved.

The issue referenced is not one that I think should be addressed in Winston. If other maintainers / the reporter disagree within the next few days, please feel free to express that. If there is no further discussion within a week, I invite the original reporter to post a public Issue here including my response.

@ranjit-git
Copy link

@wbt
I just made a comment in the report

@DABH
Copy link
Contributor

DABH commented Jan 13, 2022

I opened a separate issue for tracking this feature request. I’m leaving this issue closed though, along the lines of @wbt ‘s thinking. I phrased the new issue in a way that I think it could be addressed in Winston (the file transport code), if anyone wants to take on the work.

@ranjit-git
Copy link

Can you plz change the report status in Huntr accordingly?

@wbt
Copy link
Contributor

wbt commented Jan 13, 2022

OK, done

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

4 participants