Repository navigation
Conversation
…lnerability reporting Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XFBkWxcdHFNkD8xFdNi9Ko
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XFBkWxcdHFNkD8xFdNi9Ko
Member
Author
|
@ewaterman Sorry I'm dealing with a lot of security stuff recently so I wanted to update our default and openboxes/openboxes SECURITY.md so people go through the right channel. Since we can't assume the repositories using the default messaging have |
ewaterman
approved these changes
Oct 13, 2026
ewaterman
reviewed
Oct 13, 2026
| ## Reporting a Vulnerability | ||
|
|
||
| If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), we ask that you please email us at support@openboxes.com with details about the vulnerability. | ||
| If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), please report it privately using the **Report a vulnerability** button on the affected repository's **Security** tab, or email us at support@openboxes.com with details about the vulnerability. |
Member
There was a problem hiding this comment.
Suggested change
| If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), please report it privately using the **Report a vulnerability** button on the affected repository's **Security** tab, or email us at support@openboxes.com with details about the vulnerability. | |
| If you've uncovered a security vulnerability in the application, instead of creating a public GitHub Issue for it (which would inform potential attackers of the vulnerability), please report it privately using the **Report a vulnerability** button on the **Security and quality** tab, or email us at support@openboxes.com with details about the vulnerability. |
they'll already be within the repository when they see this message so no need to hilight the fact
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.
Keeps the org-wide default
SECURITY.mdshort, but adds GitHub private vulnerability reporting: reporters are directed to the Report a vulnerability button on the affected repository's Security tab, withsupport@openboxes.comkept as an alternative.The wording is repo-agnostic because this file is the default for every repo without its own policy (e.g.
openboxes-mobile). Private vulnerability reporting must be enabled per repo (or org-wide) for the button to appear.Companion PR: openboxes/openboxes#6244
🤖 Generated with Claude Code
https://claude.ai/code/session_01XFBkWxcdHFNkD8xFdNi9Ko