Skip to content

Security: neurabytelabs/modus

Security

SECURITY.md

Security Policy

Reporting Security Vulnerabilities

If you discover a security vulnerability in MODUS, please report it responsibly:

  1. DO NOT open a public GitHub issue
  2. Email us at: security@neurabytelabs.com
  3. Include detailed information about the vulnerability
  4. We'll respond within 48 hours

Security Measures

Environment Variables

  • All API keys and secrets are loaded via environment variables
  • No hardcoded credentials in source code
  • .env files are gitignored
  • Only .env.example with placeholder values is committed

Authentication

  • Admin authentication uses environment-based passwords
  • Production deployments require secure password setup
  • Demo mode has appropriate access controls

Dependencies

  • Regular dependency updates via Dependabot
  • Security-focused Elixir/Phoenix ecosystem
  • Docker images use official base images

Data Protection

  • Local SQLite database for development
  • Production data isolation
  • No sensitive user data collection in demo mode

Supported Versions

Version Supported
9.5.x ✅ Yes
9.4.x ❌ No
< 9.4 ❌ No

Only the latest major version receives security updates.

Security Best Practices for Users

  1. Keep your API keys secure - Never commit them to version control
  2. Use environment variables - Follow the .env.example template
  3. Update regularly - Stay on the latest supported version
  4. Production setup - Use strong admin passwords in production
  5. Network security - Use HTTPS in production deployments

Contact

For security-related questions: security@neurabytelabs.com

For general support: support@neurabytelabs.com

There aren't any published security advisories