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