|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +## Supported Versions |
| 4 | + |
| 5 | +This section outlines the versions of Byte-Lang Compiler that receive security updates. |
| 6 | +We aim to prioritize the latest stable versions to ensure optimal performance, security, and stability. |
| 7 | + |
| 8 | +| Version | Supported | |
| 9 | +| ------- | ------------------ | |
| 10 | +| 1.0.0 | :white_check_mark: | |
| 11 | + |
| 12 | +Only versions marked as supported will receive security patches and updates. |
| 13 | +Users are encouraged to upgrade to the latest version as soon as possible to benefit from security improvements. |
| 14 | + |
| 15 | +## Reporting a Vulnerability |
| 16 | + |
| 17 | +At Byte-Lang, we take security seriously. If you discover a vulnerability, please follow the reporting process outlined below: |
| 18 | + |
| 19 | +## How to Report |
| 20 | + |
| 21 | +* Send an email to richardfabianmain@gmail.com with details of the vulnerability. |
| 22 | +* Include any relevant information, including: |
| 23 | +* A detailed description of the issue. |
| 24 | +* Steps to reproduce the vulnerability. |
| 25 | +* Potential impact and risks. |
| 26 | +* Any suggested mitigations or patches (if available). |
| 27 | + |
| 28 | +Please avoid sharing the vulnerability publicly until we have resolved the issue and released a patch. |
| 29 | + |
| 30 | +## Response Timeline |
| 31 | + |
| 32 | +After reporting, you can expect: |
| 33 | + |
| 34 | +* Acknowledgment of receipt: Within 48 hours. |
| 35 | +* Initial assessment: Within 5 business days, we will inform you whether the vulnerability is valid and whether it can be reproduced. |
| 36 | +* Updates on progress: Bi-weekly updates will be provided until the issue is resolved or declined. |
| 37 | +* Resolution: Once confirmed, we will aim to release a fix within 30 days. If the issue is critical, we may expedite the process. |
| 38 | + |
| 39 | +Our Commitment |
| 40 | + |
| 41 | +* We will work with you to mitigate the issue and credit the discovery to you (unless you prefer anonymity). |
| 42 | +* If your reported vulnerability does not qualify, we will provide a detailed explanation. |
| 43 | +* In cases of significant impact, we may issue a coordinated disclosure alongside the release of a security patch. |
| 44 | + |
| 45 | +## Thank you for helping us keep Byte-Lang secure for all users! |
0 commit comments