Anduin2017 / Anduin2017/HowToCook
Trying to get in touch regarding a security issue
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 102k
- Forks
- 11.1k
- Avg merge
- 14h 21m
- Merged PRs (30d)
- 2
Description
Hey there!
I belong to an open source security research community, and a member (@aidaip) 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)
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
Start by reviewing GitHub's linked guidance on SECURITY.md and determine the repository's preferred security contact method. Add the requested SECURITY.md file with clear disclosure instructions and a contact method; the work is done when security researchers can use it to report issues responsibly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100