| Version | Supported |
|---|---|
| 0.1.x | ✅ |
We take security seriously. If you discover a security vulnerability, please report it responsibly.
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, please report them via one of these methods:
- GitHub Security Advisories: Use GitHub's private vulnerability reporting
- Email: Contact the maintainer directly (see GitHub profile)
Please include the following information:
- Type of vulnerability (e.g., SQL injection, XSS, authentication bypass)
- Step-by-step instructions to reproduce the issue
- Proof of concept or exploit code (if possible)
- Impact assessment
- Any suggested fixes
- Initial Response: Within 48 hours
- Status Update: Within 7 days
- Fix Timeline: Depends on severity, typically within 30 days for critical issues
- Acknowledgment: We'll confirm receipt of your report
- Investigation: We'll investigate and validate the issue
- Fix Development: We'll develop and test a fix
- Disclosure: We'll coordinate disclosure timing with you
- Credit: We'll credit you in the security advisory (unless you prefer anonymity)
- Never commit
.envfiles to version control - Use secrets management (e.g., Fly.io secrets, Docker secrets)
- Rotate tokens periodically
- Tokens are encrypted with AES-GCM before database storage
- Set a strong
TOKEN_ENCRYPTION_KEY(32 bytes, hex-encoded) - Generate with:
openssl rand -hex 32
- Use strong, unique passwords
- Enable SSL/TLS for database connections in production
- Restrict database access to application servers only
- Always use HTTPS in production
- Keep dependencies updated
- Monitor for security advisories in dependencies
- Access tokens expire and are automatically refreshed
- Refresh tokens are stored encrypted in the database
- Client secrets should never be exposed in logs or responses
- The service includes rate limiting via
tower_governor - Configure appropriate limits for your use case
Security updates will be released as patch versions and announced via:
- GitHub Security Advisories
- Release notes in CHANGELOG.md