Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
bc05dd9
commit b9fd50c
Showing
1 changed file
with
42 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
# Security Policies and Procedures | ||
|
||
This document outlines security procedures and general policies for the `standard` | ||
project. | ||
|
||
* [Reporting a Bug](#reporting-a-bug) | ||
* [Disclosure Policy](#disclosure-policy) | ||
* [Comments on this Policy](#comments-on-this-policy) | ||
|
||
## Reporting a Bug | ||
|
||
The `standard` team and community take all security bugs in `standard` seriously. | ||
Thank you for improving the security of `standard`. We appreciate your efforts and | ||
responsible disclosure and will make every effort to acknowledge your | ||
contributions. | ||
|
||
Report security bugs by emailing the lead maintainer at info@archerysec.com. | ||
|
||
The lead maintainer will acknowledge your email within 48 hours, and will send a | ||
more detailed response within 48 hours indicating the next steps in handling | ||
your report. After the initial reply to your report, the security team will | ||
endeavor to keep you informed of the progress towards a fix and full | ||
announcement, and may ask for additional information or guidance. | ||
|
||
Report security bugs in third-party modules to the person or team maintaining | ||
the module. | ||
|
||
## Disclosure Policy | ||
|
||
When the security team receives a security bug report, they will assign it to a | ||
primary handler. This person will coordinate the fix and release process, | ||
involving the following steps: | ||
|
||
* Confirm the problem and determine the affected versions. | ||
* Audit code to find any potential similar problems. | ||
* Prepare fixes for all releases still under maintenance. These fixes will be | ||
released as fast as possible to npm. | ||
|
||
## Comments on this Policy | ||
|
||
If you have suggestions on how this process could be improved please submit a | ||
pull request. |