We actively support security updates for the following versions:
| Version | Supported |
|---|---|
| 1.1.x | ✅ |
| 1.0.x | ❌ |
If you discover a security vulnerability, please follow these steps:
Security vulnerabilities should not be reported through public GitHub issues.
Send details to the maintainers via:
- GitHub Security Advisories (preferred)
- Direct email to repository maintainers
- Type of vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: Within 48 hours
- Initial assessment: Within 7 days
- Status updates: Every 7 days until resolved
- Resolution: Target 30 days for critical issues
Our CI/CD pipeline includes:
- Dependency scanning with
npm audit - Container scanning with Trivy
- SAST scanning for code vulnerabilities
- Secret detection to prevent credential leaks
- All secrets must use environment variables
- Dependencies are regularly updated
- Code is linted and reviewed before merge
- Admin authentication is required for sensitive operations
- Environment isolation
- Secure secret management
- HTTPS enforcement recommended
- Regular security updates applied
This is a frontend React application that processes user data locally. Key considerations:
- Data Storage: Uses browser localStorage
- Authentication: Simple password protection for admin features
- External Dependencies: Managed through npm with regular audits
- Environment Variables: Always use strong admin passwords
- HTTPS: Deploy with SSL/TLS encryption
- CSP Headers: Configure Content Security Policy
- Regular Updates: Keep dependencies current
For security-related questions or concerns, please reach out through appropriate channels listed above.