We actively support the following versions of this starter kit:
| Version | Supported |
|---|---|
| 1.x.x | ✅ |
If you discover a security vulnerability in this starter kit, please report it responsibly:
- Email: Send details to security@your-domain.com
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Response Time: We aim to respond within 48 hours
- Acknowledgment: You'll receive confirmation of receipt
- Updates: We'll keep you informed of our progress
- Credit: We'll credit you in our security advisories (unless you prefer to remain anonymous)
This project includes a security.txt file at /.well-known/security.txt with contact information for security researchers.
This starter kit includes several security measures:
- HSTS: HTTP Strict Transport Security
- CSP: Content Security Policy
- X-Frame-Options: Prevents clickjacking
- X-Content-Type-Options: Prevents MIME sniffing
- Referrer-Policy: Controls referrer information
- Permissions-Policy: Controls browser features
The CSP is configured to:
- Allow scripts from same origin and inline scripts (development)
- Allow styles from same origin, inline styles, and Google Fonts
- Allow images from same origin, data URLs, and HTTPS sources
- Allow fonts from same origin and Google Fonts
- Block object embeds and restrict frame ancestors
- Development: Relaxed CSP for development tools
- Production: Strict CSP for maximum security
-
Keep Dependencies Updated
pnpm audit pnpm update
-
Use Environment Variables
NUXT_PUBLIC_SITE_URL=https://your-domain.com
-
Review Security Headers
- Test with securityheaders.com
- Use browser dev tools to verify headers
-
Regular Security Audits
pnpm audit npm audit fix
- Use HTTPS: Always deploy with SSL/TLS
- Environment Variables: Never commit secrets
- Security Headers: Verify all headers are present
- Regular Updates: Keep dependencies and server updated
Before deploying to production:
- All dependencies updated
- No security vulnerabilities (
pnpm audit) - Environment variables configured
- HTTPS enabled
- Security headers verified
- CSP configured for production
- Security.txt accessible
- Contact information updated
For security-related questions or concerns:
- Email: security@your-domain.com
- Security.txt:
/.well-known/security.txt
Thank you for helping keep this project secure!