Last updated: 2026-05-20
- Core scan pipeline is stable; full local smoke tests and orchestrator regression tests are passing.
- Runtime Docker image is hardened using a multi-stage build and a reduced runtime footprint.
- Container security guardrail exists in CI and is configured to fail on non-base
critical/highfindings. - Base-image Debian findings are tracked under
docs/SECURITY_CONTAINER_ALLOWLIST.md.
- Application-layer Snyk code findings: remediated in current branch state.
- Container findings: remaining findings are inherited from the Debian base image supply chain.
- Medusa runtime binary is intentionally excluded from the container image until upstream dependency risk is cleared.
- CLI behavior for
--medusais now explicit: in containers without Medusa installed, it warns and skips.
- GitHub Actions billing/spend limit must be active for workflow jobs to run.
- Repository secrets required for CI container scanning:
SNYK_TOKENSNYK_ORG
- After billing/secrets are configured, run
Counterscarp Security Auditonmainto validate the guardrail end-to-end. - Internal launch preflight scripts are available:
scripts/launch_preflight.shscripts/launch_preflight.ps1
- Internal launch-day sequencing and rollback document:
docs/LAUNCH_DAY_RUNBOOK_INTERNAL.md
- README status section reflects current hardening and CI guardrail state.
- GitHub Wiki Home page should mirror this status and link to the allowlist policy.