Skip to content

Commit bb1b7e0

Browse files
committed
chore: prettier format
1 parent b91e9b7 commit bb1b7e0

File tree

1 file changed

+16
-10
lines changed

1 file changed

+16
-10
lines changed

SECURITY.md

Lines changed: 16 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,35 +2,41 @@
22

33
## Supported Versions
44

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.
67

78
| Version | Supported |
89
| ------- | ------------------ |
910
| 1.x | :white_check_mark: |
1011
| < 1.0 | :x: |
1112

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.
1316

1417
## Reporting a Vulnerability
1518

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.
1721

1822
To report a potential issue, please contact our security team at:
1923

2024
2125

2226
When reporting, please include as much detail as possible:
2327

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
2731

2832
You can expect:
2933

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
3337

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.
3541

3642
Thank you for helping us keep our project and community secure.

0 commit comments

Comments
 (0)