chore: Update security policy and reporting guidelines (#6925)

1 week ago · b4e5e2f45c
parent f2048261b2
commit b4e5e2f45c
1 changed files with 5 additions and 0 deletions
--- a/SECURITY.md
+++ b/SECURITY.md
@ -1,5 +1,9 @@
 # Security Policy

+>[!CAUTION]
+> Unfortunately, AI slop reports keep wasting my time. It will be closed and you will get banned immediately if you try to do that.
+
+
 ## Reporting a Vulnerability

 1. Please report security issues to
@ -11,6 +15,7 @@
 - Do not report any upstream dependency issues / scan result by any tools. It will be closed immediately without explanations. Unless you have PoC to prove that the upstream issue affected Uptime Kuma.
 - Do not use the public issue tracker or discuss it in public as it will cause
  more damage.
+- Do not report any SSRF issues.

 ## Do you accept other 3rd-party bug bounty platforms?