docs(security): prefer GitHub private vulnerability reporting

Surface GitHub's native private reporting workflow as the primary
disclosure channel, with security@astrolabecloud.com kept as a fallback
for reporters without a GitHub account. Updates SECURITY.md, the README
Security section, the issue-template config link, and the bug-template
warning banner.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Chris Coutinho
2026-04-29 23:09:39 +02:00
co-authored by Claude Opus 4.7
parent 8cc84ac08b
commit d6362dc773
4 changed files with 22 additions and 10 deletions
+1 -1
View File
@@ -11,7 +11,7 @@ body:
**Before submitting**, please check that:
- You're running a recent version (`uvx nextcloud-mcp-server --version` or check the Docker tag).
- The issue isn't already reported in [open issues](https://github.com/cbcoutinho/nextcloud-mcp-server/issues).
- Security issues should **not** be filed here — see [SECURITY.md](https://github.com/cbcoutinho/nextcloud-mcp-server/blob/master/SECURITY.md).
- Security issues should **not** be filed here — use [private vulnerability reporting](https://github.com/cbcoutinho/nextcloud-mcp-server/security/advisories/new) or see [SECURITY.md](https://github.com/cbcoutinho/nextcloud-mcp-server/blob/master/SECURITY.md).
- type: textarea
id: summary
+3 -3
View File
@@ -1,8 +1,8 @@
blank_issues_enabled: false
contact_links:
- name: Security vulnerability
url: https://github.com/cbcoutinho/nextcloud-mcp-server/blob/master/SECURITY.md
about: Do not file security issues publicly. Email security@astrolabecloud.com — see SECURITY.md.
- name: Security vulnerability (private report)
url: https://github.com/cbcoutinho/nextcloud-mcp-server/security/advisories/new
about: Do not file security issues publicly. Use GitHub's private vulnerability reporting, or see SECURITY.md for the email fallback.
- name: Question or discussion
url: https://github.com/cbcoutinho/nextcloud-mcp-server/discussions
about: For general questions, deployment help, or open-ended discussion, please use Discussions instead of opening an issue.