Skip to content

docs: fix org security contact routing and supported versions - #10

Merged
lewtec-bot[bot] merged 1 commit into
mainfrom
janitor/security-reporting-routing
Jul 25, 2026
Merged

docs: fix org security contact routing and supported versions#10
lewtec-bot[bot] merged 1 commit into
mainfrom
janitor/security-reporting-routing

Conversation

@lewtec-bot

@lewtec-bot lewtec-bot Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Problem

Org-wide issue chooser (contact_links) sent every security reporter to fetchurl/fetchurl private advisories, even when the finding is in an SDK, the protocol, or docs. GitHub private vulnerability reporting is per repository, so that deep-link was the wrong default for a multi-repo org.

SECURITY.md also did not say which release lines we treat as supported, so reporters had no baseline for version/backport expectations.

Change

  • Point the Security vulnerability contact link at the shared security policy and clarify that private reports belong on the affected repo
  • Add a Supported versions section for spec, server/CLI, SDKs, and docs
  • Emphasize per-repo private reporting in the Reporting section

Paths

  • SECURITY.md
  • .github/ISSUE_TEMPLATE/config.yml

Does not touch LICENSE / README.md (open #9).

Verify

  • Policy URL returns 200: https://github.com/fetchurl/.github/security/policy
  • Contact link no longer hardcodes the server advisory form
  • Docs-only; no behavior/contract change

Org-wide issue contact_links pointed every reporter at the server
repo's advisory form; private reports are per-repo. Point at the
shared security policy and spell out which release lines we treat
as supported across the multi-repo project.
@lewtec-bot
lewtec-bot Bot requested a review from lucasew July 25, 2026 07:34
@lewtec-bot
lewtec-bot Bot merged commit 723dfbd into main Jul 25, 2026
@lewtec-bot
lewtec-bot Bot deleted the janitor/security-reporting-routing branch July 25, 2026 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant