open/voyage
1
0
Fork 0
Code Issues Releases 2 Activity

docs(security): fix unreachable reporting channel and wrong repo pointer

Browse source 
Forgejo registration is disabled instance-wide, so the documented
private-issue path required an account no external reporter could
create. Add security@fromaitochitta.com as the primary channel (matches
convention in repo-standard, llm-security, .profile) and keep the
private-issue path as a secondary option for reporters who already have
an account. Also fixes the issue-tracker URL, which pointed at
open/ktg-plugin-marketplace instead of this repo's own open/voyage.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KHo7hCEHKzLCmAVRKXkJNJ
This commit is contained in:
Kjell Tore Guttormsen 2026-08-20 22:02:56 +02:00
commit 4f90aa8af0
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
SECURITY.md
View file

@ -2,13 +2,14 @@
## Reporting a vulnerability
Open a **private** issue on Forgejo:
Report privately to <security@fromaitochitta.com> — do not open a public
issue. There is no SLA — this is a solo-maintained plugin — but
acknowledged reports are usually triaged within 7 days.
> https://git.fromaitochitta.com/open/ktg-plugin-marketplace
If you already have an account on the Forgejo instance, you may instead
open a **private** issue on the repo, tagged `security`:
Tag it `security` and mark it private. Do not file public issues for
unpatched vulnerabilities. There is no SLA — this is a solo-maintained
plugin — but acknowledged reports are usually triaged within 7 days.
> https://git.fromaitochitta.com/open/voyage
## Supported versions