We take security seriously and aim to provide prompt fixes for vulnerabilities. Below are the versions of this project currently supported with security updates:
| Version | Supported |
|---|---|
| 1.x | ✅ |
| < 1.0 | ❌ |
Please ensure you’re using a supported version to receive security updates.
If you discover a security vulnerability, we encourage you to report it to us responsibly.
- Email: Please send an email to chhirolyaprince@gmail.com with details of the vulnerability.
- GitHub Issues: Avoid publicly disclosing security issues in GitHub Issues. Instead, use email for initial contact.
When reporting a vulnerability, please provide:
- A detailed description of the issue and potential impact.
- Steps to reproduce the vulnerability.
- Any relevant code snippets, logs, or screenshots.
- Your contact information for follow-up questions.
We aim to:
- Respond to vulnerability reports within 3 business days.
- Investigate and confirm the issue within 7 business days.
- Release a patch within 14 business days if the issue is confirmed.
You’ll receive updates on the status of the investigation and resolution.
To protect our users, we ask that you:
- Privately report vulnerabilities: Give us the opportunity to address the issue before making it public.
- Wait for a patch: Allow us time to develop and release a fix before disclosing the vulnerability.
Our goal is to work with the community to keep our project secure for all users.
For major security updates, we will:
- Post an advisory on the GitHub repository.
- Notify users by tagging a release that includes the fix.
We appreciate responsible disclosure and will acknowledge individuals who report security issues responsibly in our release notes. Thank you for helping us keep this project safe!