Security fixes target the current release line identified by VERSION. Older snapshots may not receive fixes, so reproduce issues against the current checkout before reporting them.

Please use GitHub's private security advisory form. Include the affected version or commit, operating system, reproduction steps, and any generated ryk audit directory if it contains only synthetic data.

Do not include real credentials, API keys, access tokens, private keys, customer data, or proprietary logs. Replace them with synthetic values.

Keep exploit details private until a fix or documented limitation is available. A design limitation may require a documentation change or a regression fixture rather than a code change.

ryk protects local agent runs that go through ryk-managed wrappers, shims, staging, policy checks, audit logging, and the stdio MCP proxy. It reduces blast radius and improves reviewability.

ryk does not make arbitrary malicious code safe, and it does not provide universal transparent filesystem or network enforcement on every operating system. Use ryk doctor for local capability status and read the compatibility matrix before making an enforcement claim.

./scripts/zig build
./scripts/zig build test
./zig-out/bin/ryk redteam --ci
./zig-out/bin/ryk doctor

Raw secrets must not appear in events.jsonl, summary.json, summary.md, replay output, red-team output, doctor output, generated policies, or release files.