| Version | Supported |
|---|---|
| 1.3.x | ✅ |
| < 1.3 | ❌ |
If you discover a security vulnerability, please do not open a public GitHub issue.
Instead, please report it by:
- Email: Contact the repository owner directly via GitHub's security advisor form
- GitHub Security Advisories: Go to the repository's "Security" tab and click "Report a vulnerability"
Please include as much detail as possible:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes (optional)
- API Key Security: Do not commit
.envfiles. The defaultOPENAI_API_KEYshould be replaced with a valid key before deployment. - Network Access: When deploying on a shared network, consider binding the server to
127.0.0.1instead of0.0.0.0to restrict access. - Session Secrets:
SESSION_SECRETis auto-generated on first launch. For production environments, set a strong custom secret in.env. - Data Privacy: All data is stored locally on the machine running the server. Ensure the server machine is properly secured and backed up.
We aim to respond to security reports within 48 hours and will keep you updated on the progress.