|
| 1 | +# Security |
| 2 | + |
| 3 | +GitHub takes the security of our software products and services seriously, |
| 4 | +including all of the open source code repositories managed through our GitHub |
| 5 | +organizations, such as [GitHub](https://github.com/GitHub). |
| 6 | + |
| 7 | +Even though |
| 8 | +[open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) |
| 9 | +and therefore not eligible for bounty rewards, we will ensure that your finding |
| 10 | +gets passed along to the appropriate maintainers for remediation. |
| 11 | + |
| 12 | +## Reporting Security Issues |
| 13 | + |
| 14 | +If you believe you have found a security vulnerability in any GitHub-owned |
| 15 | +repository, please report it to us through coordinated disclosure. |
| 16 | + |
| 17 | +**Please do not report security vulnerabilities through public GitHub issues, |
| 18 | +discussions, or pull requests.** |
| 19 | + |
| 20 | +Instead, please send an email to opensource-security[@]github.com. |
| 21 | + |
| 22 | +Please include as much of the information listed below as you can to help us |
| 23 | +better understand and resolve the issue: |
| 24 | + |
| 25 | +- The type of issue (e.g., buffer overflow, SQL injection, or cross-site |
| 26 | + scripting) |
| 27 | +- Full paths of source file(s) related to the manifestation of the issue |
| 28 | +- The location of the affected source code (tag/branch/commit or direct URL) |
| 29 | +- Any special configuration required to reproduce the issue |
| 30 | +- Step-by-step instructions to reproduce the issue |
| 31 | +- Proof-of-concept or exploit code (if possible) |
| 32 | +- Impact of the issue, including how an attacker might exploit the issue |
| 33 | + |
| 34 | +This information will help us triage your report more quickly. |
| 35 | + |
| 36 | +## Policy |
| 37 | + |
| 38 | +See |
| 39 | +[GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor#1-safe-harbor-terms) |
0 commit comments