Skip to content

Commit 1af16db

Browse files
authored
Merge pull request #2 from krraze/patch-1
Update SECURITY.md
2 parents de4d803 + b16f84d commit 1af16db

1 file changed

Lines changed: 38 additions & 19 deletions

File tree

SECURITY.md

Lines changed: 38 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,55 @@
1-
# 🔐 Security Policy
1+
# Security Policy
22

3-
## 📬 Reporting a Vulnerability
3+
## Supported Versions
44

5-
If you discover a security issue, please report it via:
5+
The following versions of this project are currently receiving security updates:
66

7-
- GitHub Security Advisory (preferred)
87

9-
Do not open public issues for vulnerabilities.
8+
> **Note:** We strongly recommend upgrading to a supported version to receive the latest security patches.
109
1110
---
1211

13-
## 📌 Scope
12+
## Reporting a Vulnerability
1413

15-
In scope:
16-
- Security vulnerabilities in the application or extension
17-
- Data leaks, auth issues, or unsafe request handling
18-
- AI-related issues (prompt injection, misuse, data exposure)
14+
If you discover a security vulnerability in this project, please follow the responsible disclosure process below.
1915

20-
Out of scope:
21-
- Theoretical issues without proof
22-
- Third-party services
16+
### How to Report
17+
18+
Send a detailed report to: **w4nn4d133@gmail.com**
19+
20+
Please include the following information in your report:
21+
22+
- A clear description of the vulnerability
23+
- Steps to reproduce the issue
24+
- Affected version(s)
25+
- Potential impact of the vulnerability
2326

2427
---
2528

26-
## ⚠️ Guidelines
29+
## What to Expect
30+
31+
| Stage | Timeline |
32+
| ----------------------------- | ------------------- |
33+
| Acknowledgement of report | Within 48 hours |
34+
| Severity assessment (CVSS v3) | Within 5 business days |
35+
| Status update | Every 7 days |
36+
| Patch release (if accepted) | Depends on severity |
2737

28-
- Provide clear steps to reproduce
29-
- Include proof-of-concept if possible
30-
- Do not publicly disclose before a fix
38+
### If Your Vulnerability Is Accepted
39+
40+
- You will be notified of the remediation plan and estimated fix timeline.
41+
- Credit will be given in the release notes (unless you prefer to remain anonymous).
42+
- A CVE identifier may be requested if applicable.
43+
44+
### If Your Vulnerability Is Declined
45+
46+
- You will receive a detailed explanation of why the report was not accepted.
47+
- You are welcome to provide additional information if you believe the decision should be reconsidered.
3148

3249
---
3350

34-
## 🛡️ Note
51+
## Responsible Disclosure
52+
53+
Please do **not** publicly disclose the vulnerability until a fix has been released or we have mutually agreed on a disclosure timeline. We are committed to working with security researchers in good faith.
3554

36-
This project is intended for ethical and defensive security research only.
55+
Thank you for helping keep this project secure. 🔒

0 commit comments

Comments
 (0)