We take the security of best-bible seriously. If you discover a vulnerability in our project, please report it to us as soon as possible.
To report a vulnerability, you can:
- Email us at best-codes@proton.me with a detailed description of the vulnerability, including steps to reproduce it and any potential impact.
- Open an issue on our GitHub repository with the "vulnerability" label and provide a clear description of the vulnerability, along with any relevant information.
We will acknowledge receipt of your report within 48 hours and will keep you informed of the progress towards resolving the vulnerability.
We are committed to providing security updates for the following versions of best-bible:
| Version | Supported |
|---|---|
| (Latest version is always supported) | ✅ |
| 1.4.5 | ✅ |
| 1.1.5 | ✅ |
| 1.0.8 | ❌ |
| 1.0.7 | ❌ |
| 1.0.6 | ❌ |
| 1.0.5 | ❌ |
| 1.0.4 | ❌ |
| 1.0.3 | ❌ |
| 1.0.2 | ❌ |
| 1.0.1 | ❌ |
| 1.0.0 | ❌ |
If you are using an older version of best-bible, we strongly recommend upgrading to a supported version to ensure you receive the latest security updates.
When a vulnerability is reported and confirmed, we will work on releasing a security update as quickly as possible. The timeline for releasing a security update may vary depending on the severity and complexity of the vulnerability.
We will keep you informed of the progress and provide an estimated timeline for the release of the security update. Once the update is available, we will notify all users and encourage them to upgrade to the latest version.
Thank you for helping us keep best-bible secure. If you have any questions or concerns regarding our security policy, please don't hesitate to reach out to us.