summaryrefslogtreecommitdiff
path: root/SECURITY.md
diff options
context:
space:
mode:
authorChristian Cleberg <[email protected]>2026-03-18 18:42:15 -0500
committerChristian Cleberg <[email protected]>2026-03-18 18:42:15 -0500
commit58b1477153186d9fa55ceb236330d1f66418be8c (patch)
tree4b38d00f8af1cdf8a34cc60f9bb60dcb71d68c20 /SECURITY.md
parent3b368f96acd0c412709c754b00e8379aebd6665b (diff)
downloadhutch-58b1477153186d9fa55ceb236330d1f66418be8c.tar.gz
hutch-58b1477153186d9fa55ceb236330d1f66418be8c.tar.bz2
hutch-58b1477153186d9fa55ceb236330d1f66418be8c.zip
revamp markdown project files
Diffstat (limited to 'SECURITY.md')
-rw-r--r--SECURITY.md50
1 files changed, 25 insertions, 25 deletions
diff --git a/SECURITY.md b/SECURITY.md
index b7e2b73..1423145 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -2,32 +2,32 @@
## Supported Versions
-This section outlines which versions of the project are currently receiving
-security updates.
+|Version|Supported|
+|-------|---------|
+| 1.x | ✅ Yes |
+| < 1.0 | ❌ No |
-| Version | Supported |
-| ------- | ------------------ |
-| 1.x | :white_check_mark: |
-| < 1.0 | :x: |
+---
## Reporting a Vulnerability
-If you discover a vulnerability, please follow the guidelines below to report
-it:
-
-1. **Submission**: Send your vulnerability report to [[email protected]].
- Please include a detailed description of the issue, steps to reproduce it,
- and any relevant context.
-
-2. **Response Time**: We aim to acknowledge reports within **3 business days**.
- You will receive updates on the status of your report throughout the process.
-
-3. **Acceptance Criteria**: If the vulnerability is confirmed, we will provide
- you with an estimated timeline for resolution and keep you informed of any
- updates until the issue is resolved.
-
-4. **Declined Reports**: If a reported vulnerability is deemed invalid or out of
- scope, we will notify you of our decision and provide reasoning for the
- decline.
-
-Thank you for helping us improve the security of our project!
+If you discover a security vulnerability, **do not open a public issue**.
+Instead:
+
+1. **Email** your report to [[email protected]](mailto:[email protected]).
+ Include:
+ - A detailed description of the vulnerability
+ - Steps to reproduce
+ - Any relevant context (e.g., affected versions, environment)
+2. **Response Time**: We will acknowledge your report within **3 business days**
+ and keep you updated on the progress.
+3. **Resolution**: If confirmed, we will:
+ - Provide an estimated timeline for a fix
+ - Work with you to verify the resolution
+ - Credit you for the discovery (if you wish)
+4. **Declined Reports**: If the report is invalid or out of scope, we will
+ explain why and close the issue.
+
+---
+
+**Thank you for helping improve the security of our project!**