Use this section to tell people about which versions of your project are currently being supported with security updates.
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
We take the security of our software seriously. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner.
- Do not create a public issue on GitHub for security vulnerabilities.
- Send an email to [INSERT EMAIL HERE] with a detailed description of the vulnerability.
- Include steps to reproduce the issue, if possible.
- Our security team will review your report and respond within 48 hours.
- We will work with you to understand and resolve the issue.
- Acknowledgement: Within 48 hours.
- Assessment: Within 5 business days.
- Fix: Timeline depends on severity, but we aim for < 14 days for critical issues.
We request that you do not publicly disclose the vulnerability until we have had reasonable time to address it. We will coordinate the public disclosure with you.
- Ensure all dependencies are up to date (
npm audit). - Do not commit secrets (API keys, passwords) to the repository.
- Use secure storage (e.g.,
SecureStorein Expo) for sensitive user data. - Validate all user inputs on both client and server sides.