repo: report a vulnerability through a GitHub security advisory or reporting-a-vulnerability@maity.team
tsk-jd3z8rr6de2t open
Oliver 2026-11-04: vulnerabilities are now reported through
- https://github.com/oliver-zehentleitner/maity/security/advisories/new
- reporting-a-vulnerability@maity.team
Changes:
SECURITY.md: replace the info@ addresses in "Reporting a vulnerability" with these two ways, advisory first. Keep the rest (confidentiality until a fix is out).- GitHub issue templates: the repo has no
.github/ISSUE_TEMPLATEyet. Add aconfig.ymlwith a contact link "Report a security vulnerability" pointing at the advisory URL, so nobody files one as a public issue. Add bug/feature templates only if they're small and obvious, otherwise leave them out. - Grep the repo (docs/, web/ texts, README, the landing/legal pages, AGENTS.md) for the old security contact and update each hit. Translated texts in every catalogue.
- Changelog fragment, KTW only if a reason needs keeping.
Small PR, normal review via vuur.