You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/SECURITY.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ Thanks for helping make GitHub safe for everyone.
4
4
5
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
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.
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
8
9
9
## Reporting Security Issues
10
10
@@ -16,13 +16,13 @@ Instead, please send an email to opensource-security[@]github.com.
16
16
17
17
Please include as much of the information listed below as you can to help us better understand and resolve the issue:
18
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
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
26
27
27
This information will help us triage your report more quickly.
0 commit comments