Skip to content

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

Open
MrBeldum wants to merge 1 commit into
ltwlf:masterfrom
MrBeldum:docs/pvr-contact-link
Open

MrBeldum wants to merge 1 commit into
ltwlf:masterfrom
MrBeldum:docs/pvr-contact-link

Conversation

@MrBeldum

@MrBeldum MrBeldum commented Oct 5, 2026

Copy link
Copy Markdown

What kind of change is this?

Docs / GitHub config (issue chooser). No library code changed.

Did you add tests for your changes?

No. This only adds .github/ISSUE_TEMPLATE/config.yml, which has no code path to test. I checked that the file parses as YAML and that the link target exists: private vulnerability reporting is enabled here (GET /repos/ltwlf/json-diff-ts/private-vulnerability-reporting returns {"enabled":true}).

Summary of changes

SECURITY.md asks reporters not to use public issues and to report a vulnerability privately instead. But there is no .github/ISSUE_TEMPLATE/config.yml, so the issue chooser does not surface that private route. A reporter has to find SECURITY.md on their own.

This adds a "Report a security vulnerability" contact link to the private advisory form, so the private route shows up in the chooser.

Other information

blank_issues_enabled: true keeps the current behaviour. The file only adds a route and doesn't remove any.

SECURITY.md asks reporters not to use public issues. Add a contact link
so the private advisory form appears in the issue chooser.
@sonarqubecloud

sonarqubecloud Bot commented Oct 5, 2026

Copy link
Copy Markdown

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