Skip to content

Security: cuesoftinc/expendit

SECURITY.md

Security Policy

Supported Versions

Security fixes are applied to the main branch. Deployed environments are expected to track main.

Reporting a Vulnerability

Do not open a public issue for security vulnerabilities.

Report privately using GitHub's private vulnerability reporting through the repository's Security → Report a vulnerability tab. CueLABS™ public repositories must enable private vulnerability reporting before publishing this policy. If that tab is unavailable, email security@cuesoft.io with the subject Security vulnerability: <repository name>. Do not disclose the vulnerability in an issue, discussion, or pull request.

Please include a description and impact, steps to reproduce, and the affected component. We aim to acknowledge within 3 business days.

Handling of Secrets

  • Never commit credentials, service-account keys, or .env files. These are covered by .gitignore and .dockerignore.
  • Supply configuration at runtime via environment variables or a secret manager — never baked into an image.

There aren't any published security advisories