| Version | Supported |
|---|---|
| 0.8.x | ✅ |
| < 0.8.0 | ❌ |
Only the latest minor release receives security patches.
Please do NOT open a public GitHub issue for security vulnerabilities.
Instead, report vulnerabilities privately via one of these methods:
- GitHub Security Advisory (preferred): use the "Report a vulnerability" button on the Security tab.
- Email: send details to the maintainer address listed in
package.json.
- Description of the vulnerability
- Steps to reproduce (or a proof-of-concept)
- Affected version(s)
- Potential impact
- Acknowledgement: within 72 hours
- Initial assessment: within 7 days
- Fix or mitigation: targeting 30 days for critical issues
- You will receive updates as the issue is triaged and resolved.
- Once a fix is released, the advisory will be published with credit (unless you prefer to remain anonymous).
- We ask that you do not publicly disclose the vulnerability until a fix is available.
- Always set a strong, unique
JWT_SECRETenvironment variable. - Run the Docker container with
security_opt: ["no-new-privileges:true"]. - Keep the host
/hostmount read-only (:ro). - Use HTTPS via a reverse proxy (nginx, Caddy, Traefik) in production.
- Regularly update to the latest release.