Skip to content

Security: RamazanKara/openexit

Security

SECURITY.md

Security Policy

OpenExit is designed for local-first assessment workflows.

Reporting Vulnerabilities

Please open a private security advisory or contact the maintainers directly. Do not publish exploit details before maintainers have had a reasonable chance to respond.

Handling Credentials

OpenExit must not store Datadog API keys, app keys, tokens, passwords, or private keys. Collectors read credentials from environment variables and redact raw source evidence before writing files.

Validation includes a conservative secret scan over generated text artifacts as well as JSON/YAML manifests. If validation reports a secret-like value, treat the bundle as unsafe to share until the value is removed or redacted.

Production Safety

OpenExit is an assessment tool. It does not apply generated configs, delete SaaS resources, or perform cutovers. Generated files are candidates and require human review.

Supported Version

The main branch is the supported development target until the first stable release.

There aren't any published security advisories