|
1 | 1 | # Security Policy |
2 | 2 |
|
3 | | -If you find a security issue in `zpe-music`, please report it privately to the repository owner rather than opening a public issue first. |
| 3 | +## Supported Scope |
| 4 | + |
| 5 | +This policy covers the `zpe-music` Python package, fixture files under |
| 6 | +`fixtures/`, proof artifacts, validation manifests, and security-sensitive repo |
| 7 | +assets such as workflows and release metadata. |
| 8 | + |
| 9 | +What counts as a security issue here: |
| 10 | + |
| 11 | +- arbitrary code execution, privilege escalation, or data exfiltration through package or dependency paths |
| 12 | +- secrets or tokens committed to the repo |
| 13 | +- vulnerable CI or release workflow behavior |
| 14 | +- supply-chain issues in declared dependencies or published artifacts |
| 15 | + |
| 16 | +What does not count as a security issue here: |
| 17 | + |
| 18 | +- benchmark losses |
| 19 | +- codec-quality regressions |
| 20 | +- documentation disputes about technical claims |
| 21 | + |
| 22 | +## Reporting |
| 23 | + |
| 24 | +Do not open a public issue for a security vulnerability. |
| 25 | + |
| 26 | +Report privately through: |
| 27 | + |
| 28 | +- GitHub Private Vulnerability Reporting |
| 29 | +- `architects@zer0pa.ai` |
4 | 30 |
|
5 | 31 | Include: |
6 | 32 |
|
7 | | -- the affected version or commit |
8 | | -- reproduction steps |
9 | | -- expected impact |
10 | | -- any proposed mitigation |
| 33 | +- affected component |
| 34 | +- reproduction steps or proof of concept |
| 35 | +- severity and impact |
| 36 | +- suggested remediation if you have one |
| 37 | + |
| 38 | +## Response Targets |
| 39 | + |
| 40 | +| Stage | Target timeframe | |
| 41 | +|---|---| |
| 42 | +| Acknowledgement | within 5 business days | |
| 43 | +| Initial triage | within 10 business days | |
| 44 | +| Remediation or mitigation plan | post-triage, based on confirmed severity | |
11 | 45 |
|
12 | | -You will receive acknowledgement after triage. Public disclosure should wait until the owner confirms the remediation plan. |
| 46 | +We follow coordinated disclosure and will not take legal action against |
| 47 | +good-faith security research that follows this policy. |
0 commit comments