Update security reporting instructions in SECURITY.md#6355
Merged
Conversation
Clarify reporting guidelines for security issues.
Owner
Author
|
@copilot Check my grammar |
Contributor
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the security reporting instructions in SECURITY.md to clarify what types of security reports should not be submitted, specifically addressing upstream dependency issues.
Key Changes
- Added a new bullet point clarifying that upstream dependency issues or tool scan results should not be reported without proof of concept (PoC) demonstrating impact on Uptime Kuma
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.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
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.
Clarify and save time in the future, because I don't want to explain again.