Repository navigation
Document private vulnerability reporting - #209
Merged
Merged
Conversation
|
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.



Change
Document the existing GitHub private vulnerability-reporting path in the default security policy. Preserve the security-maintainer statement verbatim.
The settings audit found private reporting disabled on all 11 public repositories. It is now enabled on all 11, with an independent API readback for each. Anonymous HTTP readback also confirms a Report a vulnerability entry on every public Advisories page. No report was submitted and no paid feature was enabled.
Verification
git diff --check.7b3eb7f00e8779fcf3802d7e3a14321020f554ff, with the identical reviewed treeb95aa7ea6a652f1c8efdc76becbf66d29c222991.Closes #208.