docs: point security policy at GitHub private vulnerability reporting#442
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the repository security policy to make GitHub private vulnerability reporting the primary channel, removing outdated template boilerplate and expanding guidance around coordinated disclosure and the maintainer triage/release process.
Changes:
- Replaces the personal-email-only reporting route with GitHub “Report a vulnerability” / Security Advisories flow and discourages public disclosure.
- Adds structured guidance on what to include in reports and what reporters should expect during triage → fix → release → disclosure.
- Clarifies support expectations for maintained vs. legacy release lines.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Replace the leftover GitHub-template boilerplate and the personal-email-
only reporting channel with GitHub's private vulnerability reporting
("Report a vulnerability") as the primary, coordinated-disclosure route —
the flow the project already uses for advisories. Expands the policy with
what to include in a report, what happens next, and disclosure
expectations, while preserving the existing supported-versions table and
the reproduce-before-fix / private-fix / tests-and-audits commitments.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dhensby
force-pushed
the
docs/security-policy
branch
from
11692e1 to
ce902be
Compare
jankapunkt
approved these changes
Jun 16, 2026
jankapunkt
left a comment
jankapunkt
left a comment
Member
There was a problem hiding this comment.
This is very useful indeed. We should also consider pointing issue templates and PR template to this document to avoid users disclosing zero-days via issues/PR to the public. However, we can do this in a separate PR
Contributor
Author
|
I think the GitHub UI does automatically point users to it, but not certain |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates
SECURITY.mdto make GitHub private vulnerability reporting the primary channel for reporting vulnerabilities, replacing the personal-email-only route and removing leftover GitHub-template boilerplate.Why
info@jankuester.com), which may be out of date. We'd prefer reporters use GitHub's private vulnerability reporting from now on — it's already enabled on this repo and is the flow we use in practice (e.g. GHSA-jhm7-29pj-4xvf / CVE-2026-41213).Changes
Links, the private-reporting flow, and the supported-versions table were all verified against the repo before opening.
🤖 Generated with Claude Code