Security fixes target the current 0.2.x release line and the default branch. Earlier 0.x releases may receive fixes when a safe backport is practical.

Do not open a public issue for a vulnerability. Use GitHub private vulnerability reporting when it is enabled for the public repository. Until then, contact moshe@haru.sh with a minimal reproduction and impact description.

Do not include production credentials, customer data or unrelated private source in the report.

• Generated projects contain no credentials.
• The repository contract forbids treating model output as executable shell. Current tools use typed CLI arguments and pass subprocess arguments as arrays.
• Deployment defaults to render and validate, not apply.
• CI uses read-only permissions unless a release job needs a narrow write permission.
• Autoscaling stays bounded by explicit configuration.
• Package deployment configuration rejects secret-like inline environment values and requires external references for credentials.
• Production plans require a protected CI or OIDC identity, and stale plans are rejected before apply.
• GitHub secret scanning, push protection, Dependabot security updates and CodeQL default setup protect the public repository. CI adds a failing full-history scan, dependency audit and source SBOM.

The incident response and history rewrite procedure is documented in the security gate.