Repository navigation
docs: Offer private vulnerability reporting in the issue chooser - #622
Merged
Merged
Conversation
SECURITY.md asks reporters not to open a public issue for vulnerabilities. Add a contact link so the private advisory form shows up in the issue chooser.
Collaborator
|
Hello @MrBeldum Thanks a lot for the PR. Appreciate your time and effort. Could you please sign your commits and force push? Cheers!! |
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
2 participants
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.
Summary
SECURITY.md asks reporters to use GitHub's Private Vulnerability Reporting feature. 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.
Changes
.github/ISSUE_TEMPLATE/config.ymlwith a contact link pointing tohttps://github.com/ceems-dev/ceems/security/advisories/new.blank_issues_enabled: trueso the current behaviour doesn't change. The file only adds a route.Docs / GitHub config only. No application code changed. Private vulnerability reporting is already enabled for this repository (
GET /repos/ceems-dev/ceems/private-vulnerability-reportingreturns{"enabled":true}).