Skip to content

Add private vulnerability reporting to org security policy #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jmiranda wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add private vulnerability reporting to org security policy #2

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f570863
Align org security policy with openboxes/openboxes and add private vu…
jmiranda Oct 13, 2026
0ea8193
Keep org security policy short; point to repo-level private reporting
jmiranda Oct 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Keep org security policy short; point to repo-level private reporting 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XFBkWxcdHFNkD8xFdNi9Ko
  • Loading branch information
@jmiranda @claude
jmiranda and claude committed Oct 13, 2026
commit 0ea81936bede763d47185dfea1f327322d91541e
25 changes: 1 addition & 24 deletions .github/SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,28 +1,5 @@
# Security Policy

This security policy applies to all public repositories under the [OpenBoxes](https://github.com/openboxes) organization on
GitHub.

## Supported Versions
We provide security updates for the [latest official release](https://github.com/openboxes/openboxes/releases/latest) of OpenBoxes.

## Reporting a Vulnerability

Please do not create a public GitHub Issue for a security vulnerability, since that would inform potential attackers.
Instead, report it responsibly using one of the following channels:

* **Preferred:** Submit a private report through GitHub's
[private vulnerability reporting](https://github.com/openboxes/openboxes/security/advisories/new) form.
* **Alternative:** Email [support@openboxes.com](mailto:support@openboxes.com).

## Response SLA
As an open-source project with limited resources, we will do our best to respond to and resolve security issues
in a timely manner.

We will attempt to acknowledge reports within 5–10 business days and provide a resolution within 90 days,
depending on the severity and complexity. We will also make every effort to publicly disclose all security
vulnerabilities as soon as a security update (hotfix) is available.

**Please do not disclose the issue publicly until we’ve had a chance to investigate and provide a fix.**
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.

@ewaterman ewaterman Oct 13, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


Thank you for helping make OpenBoxes safer for our users!