Add a security policy - #748
Merged
Merged
Conversation
Document how to report a vulnerability privately, using GitHub's private vulnerability reporting (now enabled on the repository), so that reports do not arrive as public issues or via a maintainer's personal email. States the supported version, what a useful report contains, and the disclosure process actually followed for CVE-2026-65321: fix privately, release to PyPI, publish the advisory the same day, credit the reporter. No response-time promise is made, since this is community-maintained. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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
Add
SECURITY.md, documenting how to report a vulnerability privately, which versions receive security fixes, and the disclosure process. Also enabled GitHub's private vulnerability reporting on the repository, which the policy points to (the Report a vulnerability button on the Security tab).WHY
CVE-2026-65321 was reported through a CNA to a maintainer's personal email, because the repository offered no documented private channel. Without one, a reporter's next-best option is a public issue, which discloses the problem before a fix exists.
The policy records the process actually followed for that report: fix privately, release to PyPI, publish the GitHub Security Advisory the same day so users are notified only once an upgrade is available, and credit the reporter. It deliberately makes no response-time promise, since the project is community-maintained.