Only the secured fork at Thibault1818/ORCH is covered by this policy. It is a private/local package and is not published to npm. Install from the fork at an audited commit or tag; do not substitute the upstream npm package.

AUDITED_COMMIT_SHA="replace-with-the-reviewed-commit-sha"
npm install -g "git+https://github.com/Thibault1818/ORCH.git#$AUDITED_COMMIT_SHA" --prefix "$TEMP_PREFIX"

• Permission bypass and the shell adapter default to disabled.
• Dangerous execution requires both the corresponding config flag and ORCHESTRY_ALLOW_DANGEROUS_EXECUTION=1.
• Prompts are sent over stdin where supported, excluded from child environments, and not persisted by default.
• Child environments are allowlisted; persisted data and terminal output are redacted.
• Worktree isolation, path containment, identifier validation, and symlink checks protect local state.
• Installation has no consumer lifecycle script and never modifies user configuration.
• Optional Claude integration requires orch setup claude-integration and explicit confirmation.
• ORCH does not install npm packages automatically or in the background. orch update only displays the secured fork's explicit update procedure.

These invariants are enforced by test/security/security-regression.test.ts and CI.

Do not open a public issue for a vulnerability. Use the fork's private security advisory form and include impact, reproduction steps, affected commit, OS, and Node.js version.

External agent CLI vulnerabilities remain the responsibility of their respective vendors.