|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +## Supported Versions |
| 4 | + |
| 5 | +| Version | Supported | |
| 6 | +| ------- | ------------------ | |
| 7 | +| 2.7.x | :white_check_mark: | |
| 8 | +| < 2.7 | :x: | |
| 9 | + |
| 10 | +## Reporting a Vulnerability |
| 11 | + |
| 12 | +We take all security bugs in `diff2html-cli` seriously. |
| 13 | +Thank you for the help improving the security of `diff2html-cli`. |
| 14 | +We appreciate your efforts and responsible disclosure and |
| 15 | +will make every effort to acknowledge your contributions. |
| 16 | + |
| 17 | +Report security bugs by emailing the lead maintainer at `rtfrodrigo [at] gmail [dot] com`. |
| 18 | + |
| 19 | +The lead maintainer will acknowledge your email within 48 hours, and will send a |
| 20 | +more detailed response within 48 hours indicating the next steps in handling |
| 21 | +your report. After the initial reply to your report, the security team will |
| 22 | +endeavor to keep you informed of the progress towards a fix and full |
| 23 | +announcement, and may ask for additional information or guidance. |
| 24 | + |
| 25 | +Report security bugs in third-party modules to the person or team maintaining |
| 26 | +the module. |
| 27 | + |
| 28 | +## Disclosure Policy |
| 29 | + |
| 30 | +When the security team receives a security bug report, they will assign it to a |
| 31 | +primary handler. This person will coordinate the fix and release process, |
| 32 | +involving the following steps: |
| 33 | + |
| 34 | + * Confirm the problem and determine the affected versions. |
| 35 | + * Audit code to find any potential similar problems. |
| 36 | + * Prepare fixes for all releases still under maintenance. These fixes will be |
| 37 | + released as fast as possible. |
| 38 | + |
| 39 | +## Comments on this Policy |
| 40 | + |
| 41 | +If you have suggestions on how this process could be improved please submit a |
| 42 | +pull request. |
0 commit comments