Trying to get in touch regarding a security issue
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.7k
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I couldn't find a SECURITY.md in your repository and am not sure how to best contact you privately to disclose a security issue.
Can you add a SECURITY.md file with an e-mail to your repository, so that our system can send you the vulnerability details? GitHub suggests that a security policy is the best way to make sure security issues are responsibly disclosed.
Once you've done that, you should receive an e-mail within the next hour with more info.
Thanks! (cc @huntr-helper)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked GitHub guidance on adding a security policy, then add SECURITY.md at the repository root with the project's private vulnerability-reporting email. Done means the file is present and gives researchers a clear contact method for responsible disclosure.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 40/100