Skip to content

Commit 636e713

Browse files
committed
chore: update SECURITY.md
1 parent 8308a20 commit 636e713

2 files changed

Lines changed: 23 additions & 5 deletions

File tree

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,5 +2,8 @@ blank_issues_enabled: false
22

33
contact_links:
44
- name: 💬 Join our Discord
5-
url: https://discord.gg/WjkQEwZHBK
5+
url: https://discord.gg/<YOUR_INVITE_CODE>
66
about: Have a question, need help, or want to chat? Join our community Discord.
7+
- name: 🔐 Report a security vulnerability
8+
url: https://github.com/@harbour-enterprises/superdoc/security/policy
9+
about: Please follow our security policy.

SECURITY.md

Lines changed: 19 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,25 @@
22

33
## Supported Versions
44

5-
| Version | Supported |
6-
| -------- | ------------------ |
7-
| > 1.10.0 | :white_check_mark: |
5+
We actively support and patch the latest minor version of SuperDoc.
6+
7+
| Version | Supported |
8+
| -------- | ------------ |
9+
| ≥ 0.15.0 | ✅ Supported |
810

911
## Reporting a Vulnerability
1012

11-
Use the [Github Vulnaribilty Reporter](https://github.com/harbour-enterprises/SuperDoc/security) tool to report your findings.
13+
If you believe you’ve found a security issue in SuperDoc, please **do not open a public GitHub issue**.
14+
15+
Instead, report it privately through [GitHub’s Security Advisories](https://github.com/harbour-enterprises/SuperDoc/security/advisories/new).
16+
This ensures the report is only visible to maintainers.
17+
18+
If you prefer email, you can also contact us at: **q@superdoc.dev**
19+
20+
## Our Process
21+
22+
- We will acknowledge receipt within **2 business days**.
23+
- We will provide a status update within **7 days**.
24+
- Once a fix is available, we’ll coordinate a responsible disclosure with you.
25+
26+
Thank you for helping keep SuperDoc and its users safe!

0 commit comments

Comments
 (0)