Skip to content

Latest commit

 

History

History
35 lines (26 loc) · 1.58 KB

CURRENT_STATUS.md

File metadata and controls

35 lines (26 loc) · 1.58 KB

Current Repository Status

Last updated: 2026-05-20

Platform Status

  • 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/high findings.
  • Base-image Debian findings are tracked under docs/SECURITY_CONTAINER_ALLOWLIST.md.

Security Posture Snapshot

  • 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 --medusa is now explicit: in containers without Medusa installed, it warns and skips.

Operational Follow-Ups

  • GitHub Actions billing/spend limit must be active for workflow jobs to run.
  • Repository secrets required for CI container scanning:
    • SNYK_TOKEN
    • SNYK_ORG
  • After billing/secrets are configured, run Counterscarp Security Audit on main to validate the guardrail end-to-end.
  • Internal launch preflight scripts are available:
    • scripts/launch_preflight.sh
    • scripts/launch_preflight.ps1
  • Internal launch-day sequencing and rollback document:
    • docs/LAUNCH_DAY_RUNBOOK_INTERNAL.md

Documentation Sync

  • README status section reflects current hardening and CI guardrail state.
  • GitHub Wiki Home page should mirror this status and link to the allowlist policy.