Skip to content
Open
Changes from all commits
Commits
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
28 changes: 28 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# Security Policy

## CRA Stewardship

This project is supported under the Linux Foundation CRA stewardship framework, as described at https://www.linuxfoundation.org/security. Security vulnerabilities should be reported through the mechanisms described below, which we will coordinate with our CRA steward. For actively exploited vulnerabilities and severe incidents that may require CRA escalation, please use the project’s emergency security reporting mechanisms as appropriate.
Comment thread
bact marked this conversation as resolved.

## Reporting a Vulnerability

We take the security of this project seriously. If you believe you have found a security vulnerability, please do not report it publicly through a GitHub issue.

Instead, please send a confidential email with details of the vulnerability and a reference to this tool-java repository to:
[spdx-tools-security@lists.spdx.org](mailto:spdx-tools-security@lists.spdx.org)
Comment thread
bact marked this conversation as resolved.
Comment on lines +11 to +12

@bact bact Oct 1, 2026 •

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
Instead, please send a confidential email with details of the vulnerability and a reference to this tool-java repository to:
[spdx-tools-security@lists.spdx.org](mailto:spdx-tools-security@lists.spdx.org)
Instead, please send a confidential email with details of the vulnerability and a reference to this `tools-java` repository to:
<spdx-tools-security@lists.spdx.org>.
This is a private, restricted mailing list accessible only to authorized security maintainers.

@goneall what about this?


### What to Include

To help us quickly understand and address the issue, please include as much of the following information as possible:

* Type of issue (e.g., buffer overflow)
Comment thread
goneall marked this conversation as resolved.
* Full paths of source file(s) related to the manifestation of the issue
* Any special configuration required to reproduce the issue
* Step-by-step instructions or a proof-of-concept to reproduce the issue
* Impact of the issue, including how an attacker could exploit it

### Response & Handling Process

* **Acknowledgment:** We will acknowledge receipt of your vulnerability report within a reasonable timeframe.
Comment thread
goneall marked this conversation as resolved.
* **Investigation:** The maintainers will investigate the issue and determine its impact and scope.
* **Fix & Disclosure:** Once a fix is prepared and tested, a security update will be released. We appreciate your cooperation in keeping the vulnerability confidential until a patch is publicly available.
Loading