| Version | Supported |
|---|---|
| main | ✅ |
We take security seriously. If you discover a security vulnerability, please report it responsibly.
Please do NOT report security vulnerabilities through public GitHub issues.
Instead, please report them via email or GitHub's private vulnerability reporting:
-
GitHub Security Advisories (Preferred): Use GitHub's private vulnerability reporting
-
Email: Contact the maintainers directly
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
- Acknowledgment: Within 48 hours
- Initial Assessment: Within 1 week
- Resolution Timeline: Depends on severity, typically 30-90 days
The following are in scope:
- Backend API vulnerabilities
- Frontend security issues (XSS, CSRF, etc.)
- Authentication/authorization bypasses
- Data exposure risks
- Dependency vulnerabilities
- Vulnerabilities in third-party services (MAST Portal, etc.)
- Social engineering attacks
- Physical security
- Denial of service attacks
- Environment Variables: Always use
.envfiles for credentials, never commit them - Production Passwords: Use strong, unique passwords for MongoDB in production
- Network Security: Don't expose MongoDB or internal services to the public internet
- Updates: Keep Docker images and dependencies updated
We appreciate responsible disclosure and will acknowledge security researchers who report valid vulnerabilities.