Skip to content

Security: edithatogo/mars

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.0.x
< 1.0

Reporting a Vulnerability

We take the security of mars seriously. If you discover a security vulnerability, please follow these steps:

  1. Do NOT open a public issue.
  2. Email the maintainer directly at: dylan@mordaunt.dev
  3. Include the following in your report:
    • Description of the vulnerability
    • Steps to reproduce
    • Potential impact
    • Suggested fix (if any)

Response Timeline

  • Initial Response: Within 48 hours
  • Vulnerability Assessment: Within 1 week
  • Fix Released: Within 2 weeks (for critical issues)

Security Best Practices for Users

  • Always install mars in a virtual environment
  • Keep mars updated to the latest version
  • Review dependency licenses before use in production
  • Use the latest Python version supported

Security Measures

This project currently implements:

  • Bandit for static security analysis
  • Safety for dependency vulnerability checking
  • GitHub-hosted workflow automation for CI and release validation

Future hardening work may add SBOM generation, release signing, and provenance once those controls are implemented end-to-end.

There aren’t any published security advisories