Skip to content

Commit 27cfc90

Browse files
Create SECURITY.md (#1892)
Added a security policy document outlining reporting procedures for vulnerabilities.
1 parent 3322a64 commit 27cfc90

File tree

1 file changed

+39
-0
lines changed

1 file changed

+39
-0
lines changed

SECURITY.md

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
We provide security updates for the latest stable minor release line.
6+
7+
| Version | Supported |
8+
| -------- | --------- |
9+
| 0.49.x ||
10+
| < 0.49.x ||
11+
12+
> Note: Pre-releases, development builds, and commits on `main` are not considered supported release versions. If you believe you have found a vulnerability in unreleased code, please still report it following the process below.
13+
14+
## Reporting a Vulnerability
15+
16+
Please report security issues **privately** using the GitHub Security Advisory tool to create a new draft advisory:
17+
18+
- https://github.com/bitsandbytes-foundation/bitsandbytes/security/advisories/new
19+
20+
Do not open a public GitHub issue for security-sensitive reports.
21+
22+
### What to include
23+
24+
To help us triage and respond quickly, please include:
25+
26+
- A clear description of the issue and potential impact
27+
- Affected version(s) and environment details (OS, GPU type, CUDA version, Python version, PyTorch version, etc)
28+
- Steps to reproduce (ideally a minimal proof of concept)
29+
- Any relevant logs, crash traces, or screenshots
30+
- Any known mitigations or workarounds
31+
32+
## Response process
33+
34+
We will review reports filed via GitHub Security Advisories and collaborate with the reporter in the advisory thread to:
35+
36+
- Confirm and reproduce the report
37+
- Assess severity and affected versions
38+
- Identify mitigations and/or prepare a fix
39+
- Coordinate any follow-up needed prior to broader communication

0 commit comments

Comments
 (0)