Until v1.0.0, security fixes target the newest published minor release. Maintainers may provide a migration rather than backport a fix when pre-1.0 protocol behavior changes.

Use GitHub's private security advisory flow for asimons81/hardproof. Do not open a public issue for a vulnerability that could expose secrets, bypass approvals, corrupt state, execute unintended commands, or weaken evidence integrity.

Include affected versions, environment, reproduction steps, impact, and any suggested mitigation. Remove real credentials and private data. Maintainers will acknowledge the report, assess severity, coordinate remediation, and credit reporters who consent.

Hardproof is process control, not a security sandbox. It uses project-local state, no telemetry, no hosted dependency, explicit human approval surfaces, bounded redacted output, path containment, forward-only migrations, and workspace-bound evidence. See docs/security-model.md for trust boundaries and limitations.

All public Hardproof releases are cryptographically signed. Verify a release tag:

git config gpg.format ssh
git config gpg.ssh.allowedSignersFile .github/release-signers
git tag -v v0.1.1

Published tags are never moved. If a release has an error, a new patch version is cut. See docs/security/release-signing.md for the full signing policy, approved signers, key rotation, and compromise procedures.