|
2 | 2 |
|
3 | 3 | ## Supported Versions |
4 | 4 |
|
5 | | -The following table lists the versions of our project that are currently supported with security updates. |
| 5 | +The following table lists the versions of our project that are |
| 6 | +currently supported with security updates. |
6 | 7 |
|
7 | 8 | | Version | Supported | |
8 | 9 | | ------- | ------------------ | |
9 | 10 | | 1.x | :white_check_mark: | |
10 | 11 | | < 1.0 | :x: | |
11 | 12 |
|
12 | | -We strongly recommend keeping your installation up to date with the latest stable release to ensure you receive all security patches and improvements. |
| 13 | +We strongly recommend keeping your installation up to date with the |
| 14 | +latest stable release to ensure you receive all security patches and |
| 15 | +improvements. |
13 | 16 |
|
14 | 17 | ## Reporting a Vulnerability |
15 | 18 |
|
16 | | -If you discover a security vulnerability, we greatly appreciate your help in responsibly disclosing it. |
| 19 | +If you discover a security vulnerability, we greatly appreciate your |
| 20 | +help in responsibly disclosing it. |
17 | 21 |
|
18 | 22 | To report a potential issue, please contact our security team at: |
19 | 23 |
|
20 | 24 | |
21 | 25 |
|
22 | 26 | When reporting, please include as much detail as possible: |
23 | 27 |
|
24 | | -* Steps to reproduce the vulnerability |
25 | | -* Potential impact or risk level |
26 | | -* Any relevant code snippets or configurations |
| 28 | +- Steps to reproduce the vulnerability |
| 29 | +- Potential impact or risk level |
| 30 | +- Any relevant code snippets or configurations |
27 | 31 |
|
28 | 32 | You can expect: |
29 | 33 |
|
30 | | -* **Initial acknowledgment** within **48 hours** |
31 | | -* **Regular updates** (at least weekly) on the status of your report |
32 | | -* **Notification** once the issue is verified, mitigated, or resolved |
| 34 | +- **Initial acknowledgment** within **48 hours** |
| 35 | +- **Regular updates** (at least weekly) on the status of your report |
| 36 | +- **Notification** once the issue is verified, mitigated, or resolved |
33 | 37 |
|
34 | | -If the vulnerability is confirmed, we will prioritize it for patching and release a fix as soon as possible. If it is not accepted as a valid security issue, we will explain our reasoning clearly. |
| 38 | +If the vulnerability is confirmed, we will prioritize it for patching |
| 39 | +and release a fix as soon as possible. If it is not accepted as a |
| 40 | +valid security issue, we will explain our reasoning clearly. |
35 | 41 |
|
36 | 42 | Thank you for helping us keep our project and community secure. |
0 commit comments