Who to contact for security issues
See original GitHub issueHey there!
I belong to an open source security research community, and a member (@sampaguitas) 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)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Report a security or privacy vulnerability
Alternatively, you can send your research to us via email at product-security@apple.com. Please make sure that you include the information ...
Read more >Report an Incident
If you believe someone is using your Social Security number, contact the Social Security Administration (SSA) fraud hotline at 1-800-269-0271.
Read more >Online Safety | USAGov
Online security and safety; Internet Fraud ... Call USAGov at 1-844-USA-GOV1 (1-844-872-4681) to ask us any question about the U.S. government for free....
Read more >Cyber Crime — FBI
Respond and Report · File a Report with the Internet Crime Complaint Center · Contact Your Local FBI Field Office.
Read more >Social Security: Fraud Prevention and Reporting | SSA
Failing to notify the agency of the death of a beneficiary and continuing to ... using your SSN and assuming your identity can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rexxars - sorted:
https://github.com/CVEProject/cvelist/pull/5853/files
To summarize:
This ensures that people do not have to upgrade to v2 if they are stuck on the v1 range, due to needing support for node 12 or below, or similar.
Would be great if you could update the CVE.