| Version | Supported |
|---|---|
| 0.1.x | ✅ |
If you discover a security vulnerability in Trafic, please report it by emailing security@studiometa.fr.
Please include:
- A description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes (optional)
- Acknowledgment within 48 hours
- Status update within 7 days
- Fix timeline depends on severity:
- Critical: 24-48 hours
- High: 1 week
- Medium: 2 weeks
- Low: Next release
We ask that you:
- Give us reasonable time to fix the issue before public disclosure
- Avoid accessing or modifying data that isn't yours
- Act in good faith to avoid privacy violations, data destruction, or service disruption
We will:
- Respond promptly to your report
- Keep you informed of our progress
- Credit you in the release notes (unless you prefer anonymity)
When deploying Trafic:
- Use SSH keys — Never use password authentication
- Restrict SSH access — Use
AllowUsersin sshd_config - Enable Let's Encrypt — Always use HTTPS in production
- Configure authentication — Don't use
allowpolicy for public-facing previews - Keep updated — Run
npm updateregularly for security patches - Firewall — Only expose ports 22, 80, and 443
See the setup command for automated server hardening.