Skip to content

docs: Offer private vulnerability reporting in the issue chooser - #545

Closed
Daniel Bae (MrBeldum) wants to merge 1 commit into
Quantco:mainfrom
MrBeldum:docs/issue-chooser-security-link
Closed

Daniel Bae (MrBeldum) wants to merge 1 commit into
Quantco:mainfrom
MrBeldum:docs/issue-chooser-security-link

Conversation

@MrBeldum

Copy link
Copy Markdown

Summary

SECURITY.md asks reporters to use the private advisory form, but .github/ISSUE_TEMPLATE/config.yml only set blank_issues_enabled: false and had no contact link, so the issue chooser showed the public issue template with no private security route.

This adds a contact link to the private advisory form so that route appears in the chooser. Private vulnerability reporting is already enabled for this repository (GET /repos/Quantco/tabmat/private-vulnerability-reporting returns {"enabled":true}).

blank_issues_enabled stays false (existing behaviour).

Changes

  • Add a "Report a security vulnerability" contact link in .github/ISSUE_TEMPLATE/config.yml pointing at https://github.com/Quantco/tabmat/security/advisories/new.
  • Keep blank_issues_enabled: false.

Checklist

  • Docs / GitHub config only — no application code changed.
  • Verified private vulnerability reporting is enabled on this repository.

SECURITY.md directs reporters to the private advisory form, but
.github/ISSUE_TEMPLATE/config.yml only set blank_issues_enabled and had no
contact link for it. Add that link so the private route shows up in the
issue chooser. Private vulnerability reporting is already enabled for this
repository.
@jtilly

Copy link
Copy Markdown
Member

I think the current process is sufficiently clear:

Screen.Recording.2026-10-05.at.11.54.43.PM.mov

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.

2 participants