We release patches for security vulnerabilities in the following versions:
Version | Supported |
---|---|
1.0.x | ✅ |
< 1.0 | ❌ |
If you discover a security vulnerability within this project, please follow these steps:
- Do not open an issue on GitHub.
- Send an email to [email protected] with the details of the vulnerability.
- Include the following information:
- A description of the vulnerability.
- Steps to reproduce the vulnerability.
- Any potential impact or exploit scenarios.
- Your contact information.
We will respond to your report within 72 hours with an acknowledgment and will work with you to understand and resolve the issue as quickly as possible.
To ensure the security of your deployment, please follow these best practices:
- Environment Variables: Keep your
.env
file secure and do not expose it in your version control system. - Dependencies: Regularly update your dependencies to the latest versions to ensure you have the latest security patches.
- HTTPS: Always use HTTPS to encrypt data in transit.
- Authentication: Use strong authentication mechanisms and regularly rotate credentials.
- Authorization: Implement proper authorization checks to ensure users can only access resources they are permitted to.
- Validation: Validate all user inputs to prevent common vulnerabilities such as SQL injection and XSS.
- Monitoring: Monitor your application for suspicious activity and set up alerts for potential security incidents.
For any security-related inquiries, please contact [email protected].
Thank you for helping to keep this project secure.