This section outlines the versions of our project that are currently supported with security updates.
| Version | Supported |
|---|---|
| 3.0.x | ✅ |
| 2.5.x | |
| 2.4.x | |
| 2.3.x | ✖️ |
| 2.2.x | ✖️ |
| 2.1.x | ✖️ |
| 2.0.x | ✖️ |
| 1.6.x | ❌ |
| 1.5.x | ❌ |
| 1.4.x | ❌ |
| 1.3.x | ❌ |
| 1.2.x | ❌ |
| 1.1.x | ❌ |
| 1.0.x | ❌ |
| Key | Desc |
|---|---|
| ✅ | Supported for security updates |
| Supported, but will leave support next major update | |
| ✖️ | Only for major security issues (CVSS 8.0+) |
| ❌ | No longer supported for security updates |
If you believe you have found a security vulnerability in our project, we encourage you to report it to us. Your report will help us improve the security of our project and ensure the trust of our users.
- Identify the Vulnerability: Clearly describe the vulnerability, including how it can be exploited and any potential impact.
- Provide Detailed Information: Include as much detail as possible, such as the version of the project affected, steps to reproduce the vulnerability, and any relevant code snippets or screenshots.
- Contact Us: Send your report to my email. Please include "Security Vulnerability Report" in the subject line.
- Acknowledgment: Upon receiving your report, we will acknowledge receipt within 2�5 business days.
- Investigation: Our security team will investigate the vulnerability and determine its validity.
- Update: If the vulnerability is accepted, we will work on a fix and provide an update on the timeline for a security update.
- Communication: We will communicate with you regarding the status of the vulnerability and any necessary actions.
- The vulnerability must be reproducible.
- The vulnerability must be exploitable.
- The vulnerability must not be a false positive.
- The vulnerability is outside the scope of our project.
Thank you for helping us maintain the security of our project. Your contribution is invaluable in keeping our users safe.