Security fixes are provided on the default branch and any currently maintained release branches. Archived repositories are not actively maintained unless their README states otherwise.
Do not open a public issue for a suspected vulnerability.
Report it privately through this repository's GitHub Security Advisories:
→ Open the repository's Security tab → Advisories → "Report a vulnerability".
If that option is unavailable, private vulnerability reporting is not enabled here yet. Open a brief public issue containing no vulnerability details — just ask a maintainer to turn on private reporting — then send the details privately once it is enabled.
Please include:
- affected repository and branch or version
- reproduction steps or a proof of concept
- expected impact
- any known public-disclosure timeline
Maintainers acknowledge valid reports within 3 business days, provide an initial triage result within 10 business days, and keep you updated until the issue is fixed, accepted as risk, or declined with a rationale.
Treat validation.local as untrusted code when a public pull request can affect .ai/config.json,
test files, package scripts, build tooling, or any command it runs. Host validation on a
self-hosted runner can become remote code execution with that runner's filesystem, environment,
network, and credential permissions.
ORC strongly recommends validation.isolation=container, which runs local validation in the
network-denied container sandbox when Docker or Podman is available. If ORC falls back to
validation.isolation=host, use a minimal-permission runner with no broad cloud, package-registry,
or production credentials, and treat the warning as a security exception to remove before accepting
untrusted public PRs.
See Validation Isolation for the container-vs-host trade-off and the recommended public-repo posture.
Good-faith research that avoids privacy violations, service disruption, data destruction, and public disclosure before remediation is authorized by the maintainers is welcome.