Create SECURITY.md
This commit is contained in:
parent
ce88d603fc
commit
c6624a3fcf
1 changed files with 42 additions and 0 deletions
42
SECURITY.md
Normal file
42
SECURITY.md
Normal file
|
|
@ -0,0 +1,42 @@
|
|||
# Security Policy
|
||||
|
||||
## Supported Versions
|
||||
|
||||
| Version | Supported |
|
||||
| ------- | ------------------ |
|
||||
| 2.9.x | :white_check_mark: |
|
||||
| < 2.9 | :x: |
|
||||
|
||||
## Reporting a Vulnerability
|
||||
|
||||
We take all security bugs in `diff2html` seriously.
|
||||
Thank you for the help improving the security of `diff2html`.
|
||||
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 `rtfrodrigo [at] gmail [dot] 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.
|
||||
|
||||
## Comments on this Policy
|
||||
|
||||
If you have suggestions on how this process could be improved please submit a
|
||||
pull request.
|
||||
Loading…
Reference in a new issue