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