Please do not open a public GitHub issue for security-sensitive findings. Instead use one of:

1. Preferred — open a private GitHub Security Advisory on this repo.
2. Email the maintainer at the address listed on the GitHub profile linked from the repo.

You should receive an acknowledgement within 3 business days and a remediation timeline within 7 business days. orbiter follows coordinated disclosure: we'll work with you on a public advisory after the fix ships.

In scope:

• Sandbox escapes (a Patch causing pytest to execute outside the intended snapshot tree).
• Path traversal in RepoView.apply_patch despite the inside-repo-root check.
• Token / credential leakage via logs, run-state, or PR artefacts.
• Prompt-injection paths that cause the Surgeon to apply a patch the Verifier would reject in a non-mock setting.

Out of scope:

• Issues that require an attacker who already has shell access on the user's machine.
• Issues in upstream dependencies (please report those upstream).
• Mock-mode-only behaviour, which is deterministic by design and not a trust boundary.