We release patches for security vulnerabilities in the following versions:
| Version | Supported |
|---|---|
| 0.7.x | ✅ |
| 0.6.x | ✅ |
| < 0.6 | ❌ |
We take the security of OrKa seriously. If you believe you have found a security vulnerability in OrKa, please report it to us as described below.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them via email to: [security@yourproject.com] (replace with your actual email)
You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
Please include the following information in your report:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
- Your report will be acknowledged within 48 hours
- We will investigate and validate the issue
- We will work on a fix and determine the release timeline
- We will notify you when the fix is released
- We may ask for additional information or guidance during the process
We prefer all communications to be in English.
Security updates will be released as patch versions and announced through:
- GitHub Security Advisories
- Release notes
- Project documentation updates
If you have suggestions on how this process could be improved, please submit a pull request or create an issue.