|
1 | 1 | # Security Policy |
2 | 2 |
|
3 | | -## Supported versions |
| 3 | +## Supported Versions |
4 | 4 |
|
5 | | -Until a stable versioning policy is established, only the latest tagged release is considered supported for security fixes. |
| 5 | +Security fixes are applied to the `main` branch. |
6 | 6 |
|
7 | | -## Reporting a vulnerability |
| 7 | +| Version | Supported | |
| 8 | +| --- | --- | |
| 9 | +| `main` | :white_check_mark: | |
| 10 | +| Other branches/tags | :x: | |
8 | 11 |
|
9 | | -Please do **not** open public GitHub issues for sensitive security reports. |
| 12 | +## Reporting a Vulnerability |
10 | 13 |
|
11 | | -Instead: |
| 14 | +Please do **not** open public GitHub issues for undisclosed security findings. |
12 | 15 |
|
13 | | -1. open a private security advisory if available for the repository, or |
14 | | -2. contact the maintainer directly with a concise reproduction and impact summary |
| 16 | +Use GitHub Private Vulnerability Reporting for this repository: |
| 17 | +<https://github.com/Prekzursil/codex-session-manager/security/advisories/new> |
15 | 18 |
|
16 | | -Include: |
| 19 | +If private advisory reporting is unavailable, contact the maintainer privately on GitHub (`@Prekzursil`). |
17 | 20 |
|
18 | | -- affected version or commit |
19 | | -- reproduction steps |
20 | | -- expected vs actual behavior |
21 | | -- whether the issue can expose private local session content, metadata, or unsafe maintenance behavior |
| 21 | +When reporting, include: |
22 | 22 |
|
23 | | -## Security expectations for contributors |
| 23 | +- the affected component, file, workflow, or dependency |
| 24 | +- the exact commit, branch, or release if known |
| 25 | +- clear reproduction or proof-of-concept steps |
| 26 | +- impact details covering confidentiality, integrity, or availability |
| 27 | +- any suggested mitigation if known |
24 | 28 |
|
25 | | -- do not add telemetry or network sync without explicit review |
26 | | -- do not weaken maintenance confirmations or checkpoint creation |
27 | | -- do not make live Codex SQLite state writable in v1 |
28 | | -- do not add real personal session data to tests, docs, fixtures, or screenshots |
| 29 | +## Disclosure Expectations |
| 30 | + |
| 31 | +- Initial acknowledgment: best effort within 3 business days. |
| 32 | +- Triage update: best effort within 7 business days. |
| 33 | +- Coordinated disclosure is expected; please allow time to investigate and patch before public disclosure. |
0 commit comments