|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +## Supported Versions |
| 4 | + |
| 5 | + |
| 6 | +| Version | Supported | PHP Version | |
| 7 | +|---------|--------------------|------------------------------------------------------------------------------------------------------------------------| |
| 8 | +| 5.x | :white_check_mark: |  | |
| 9 | +| 4.x | :white_check_mark: |  | |
| 10 | +| <= 3.x | :x: | | |
| 11 | + |
| 12 | + |
| 13 | +## Reporting Potential Security Issues |
| 14 | + |
| 15 | +If you have encountered a potential security vulnerability in this project, |
| 16 | +please report it to us at <security@dotkernel.com>. We will work with you to |
| 17 | +verify the vulnerability and patch it. |
| 18 | + |
| 19 | +When reporting issues, please provide the following information: |
| 20 | + |
| 21 | +- Component(s) affected |
| 22 | +- A description indicating how to reproduce the issue |
| 23 | +- A summary of the security vulnerability and impact |
| 24 | + |
| 25 | +We request that you contact us via the email address above and give the |
| 26 | +project contributors a chance to resolve the vulnerability and issue a new |
| 27 | +release prior to any public exposure; this helps protect the project's |
| 28 | +users, and provides them with a chance to upgrade and/or update in order to |
| 29 | +protect their applications. |
| 30 | + |
| 31 | + |
| 32 | +## Policy |
| 33 | + |
| 34 | +If we verify a reported security vulnerability, our policy is: |
| 35 | + |
| 36 | +- We will patch the current release branch, as well as the immediate prior minor |
| 37 | + release branch. |
| 38 | + |
| 39 | +- After patching the release branches, we will immediately issue new security |
| 40 | + fix releases for each patched release branch. |
| 41 | + |
0 commit comments