Skip to content

Commit cd6b5b6

Browse files
qwerty541devantler
authored andcommitted
Docs: Add security policy (anuraghazra#2908)
1 parent 7beae68 commit cd6b5b6

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

SECURITY.md

+39
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# GitHub Readme Stats Security Policies and Procedures <!-- omit in toc -->
2+
3+
This document outlines security procedures and general policies for the
4+
GitHub Readme Stats project.
5+
6+
- [Reporting a Vulnerability](#reporting-a-vulnerability)
7+
- [Disclosure Policy](#disclosure-policy)
8+
9+
## Reporting a Vulnerability
10+
11+
The GitHub Readme Stats team and community take all security vulnerabilities
12+
seriously. Thank you for improving the security of our open source
13+
software. We appreciate your efforts and responsible disclosure and will
14+
make every effort to acknowledge your contributions.
15+
16+
Report security vulnerabilities by emailing the GitHub Readme Stats team at:
17+
18+
```
19+
20+
```
21+
22+
The lead maintainer will acknowledge your email within 24 hours, and will
23+
send a more detailed response within 48 hours indicating the next steps in
24+
handling your report. After the initial reply to your report, the security
25+
team will endeavor to keep you informed of the progress towards a fix and
26+
full announcement, and may ask for additional information or guidance.
27+
28+
Report security vulnerabilities in third-party modules to the person or
29+
team maintaining the module.
30+
31+
## Disclosure Policy
32+
33+
When the security team receives a security bug report, they will assign it
34+
to a primary handler. This person will coordinate the fix and release
35+
process, involving the following steps:
36+
37+
* Confirm the problem.
38+
* Audit code to find any potential similar problems.
39+
* Prepare fixes and release them as fast as possible.

0 commit comments

Comments
 (0)