|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +This document describes how to report security issues for BugleOS Cross Toolchain. |
| 4 | + |
| 5 | +## Supported Versions |
| 6 | + |
| 7 | +We currently support the latest released version and the `main` branch. |
| 8 | + |
| 9 | +| Version | Supported | |
| 10 | +| --- | --- | |
| 11 | +| latest | :white_check_mark: | |
| 12 | +| older releases | :x: | |
| 13 | + |
| 14 | +## Reporting a Vulnerability |
| 15 | + |
| 16 | +Please report security issues **privately**. |
| 17 | + |
| 18 | +Preferred method: |
| 19 | +1. Open a private GitHub Security Advisory: |
| 20 | + https://github.com/strombetta/bugleos-make-toolchain/security/advisories |
| 21 | + |
| 22 | +If you cannot use GitHub Security Advisories, contact the maintainer privately |
| 23 | +via the email listed in the maintainer's GitHub profile or commit metadata. |
| 24 | + |
| 25 | +### What to Include |
| 26 | + |
| 27 | +Please include: |
| 28 | +- A clear description of the vulnerability and impact |
| 29 | +- Steps to reproduce (proof-of-concept if possible) |
| 30 | +- Affected versions/commits |
| 31 | +- Any suggested fixes or mitigations |
| 32 | + |
| 33 | +## Response Timeline |
| 34 | + |
| 35 | +We aim to: |
| 36 | +- Acknowledge receipt within **2 business days** |
| 37 | +- Provide a status update within **7 days** |
| 38 | +- Coordinate a fix and disclosure schedule as appropriate |
| 39 | + |
| 40 | +Timelines may vary based on complexity and upstream coordination needs. |
| 41 | + |
| 42 | +## Scope |
| 43 | + |
| 44 | +In scope: |
| 45 | +- Build scripts, CI workflows, release artifacts, and integrity checks |
| 46 | +- Supply-chain or signing/verification issues |
| 47 | +- Toolchain configuration that could compromise build outputs |
| 48 | + |
| 49 | +Out of scope: |
| 50 | +- Vulnerabilities in upstream projects (binutils/GCC/musl/Linux) |
| 51 | + unless introduced or amplified by this repository |
| 52 | + |
| 53 | +## Coordinated Disclosure |
| 54 | + |
| 55 | +Please do not open public issues or disclose details until a fix or mitigation |
| 56 | +is available. We will coordinate disclosure with you. |
| 57 | + |
| 58 | +## Security Updates |
| 59 | + |
| 60 | +Security fixes will be released as new versions. Release notes will reference |
| 61 | +the advisory and provide upgrade guidance. |
0 commit comments