ReleaseGate is an experimental research artifact. It has not undergone a production security audit and does not make autonomous promotion safe.

Bench scoring is offline and should run without infrastructure credentials. Core sends rendered benchmark inputs to whichever model provider the operator configures. Stack can create and delete Dokploy staging projects and dispatch a signed promotion-intent webhook. Treat those capabilities as privileged.

Security fixes are applied to the latest release on the default branch. Frozen benchmark snapshots remain immutable; a correction affecting their contents is published as a new version with an erratum.

Do not open a public issue for leaked or suspected credentials, an authorization bypass, unintended production mutation or destructive cleanup, prompt-injection behavior that exposes secrets, a way to forge or replay promotion webhooks, or personal data that should be removed from a frozen artifact.

Use GitHub's Security → Report a vulnerability private-reporting flow for pmdlt/ReleaseGate. Include the affected path/version, impact, reproduction steps, and any suggested mitigation. Do not include real credentials, production identifiers, or unnecessary personal data.

If private reporting is unavailable, open a minimal issue asking the maintainer to enable a private channel; do not disclose exploit details.

• Use a disposable Dokploy environment and least-privilege credentials.
• Keep .env files untracked and outside logs or chat transcripts.
• Leave the promotion webhook unset until its receiver verifies HMAC, timestamp, nonce, target allowlist, and human/operational policy.
• Use HTTPS for Dokploy, Windmill, object storage, and webhook traffic.
• Rotate credentials after demos and immediately after suspected exposure.
• Inspect exact project and compose targets before any destructive action.
• Never mount a Docker socket into an LLM-controlled worker.

The Apache-2.0 and CC BY 4.0 artifacts are provided without warranty.