Report a suspected vulnerability through GitHub's Report a vulnerability action on this repository's Security tab when private reporting is enabled. If unavailable, open an issue asking for a private contact without posting exploit details, credentials, or private user data. Maintainers will coordinate a private channel before sensitive material is shared.

The current 0.x series is maintained through the latest release. No response-time guarantee or paid support agreement is implied.

faac executes approved shell commands without a sandbox. Such commands can access external files and services. File tools validate workspace paths, permissions, and expected hashes, but shell approval grants the full authority of the command. Run the agent with the least account access needed.

Credentials belong in environment variables, a secret manager, or faac's passphrase-encrypted vault. Do not pass them in prompt arguments, commit them in configuration, or attach raw transcripts to reports. Redaction reduces accidental disclosure; it cannot prove an arbitrary document contains no secrets.

Upstream synchronization fetches into a faac-owned Git cache and parses a bounded subset of source as data. It never imports fetched TypeScript, installs upstream packages, or runs repository scripts. Unknown compatibility changes quarantine the affected integration.

PR text and source are untrusted inputs. Eligible PR jobs run with read-only permissions and no provider or publication secrets. Explicit Copilot tasks use a process-scoped token, one chosen model, and durable submission receipts; there is no delivery controller or label-driven task execution.

All five CI jobs run only for PRs into develop or hotfix PRs into main. Ordinary promotion skips them all; the coordinator preserves the validated source tree. Explicit release validation proves that tree passed eligible PR checks before allowing publication. Publication uses trusted main code and artifact integrity checks without rerunning quality/security jobs. Do not bypass branch protections or accept an error comment as completed review. See DevOps.

Rotate a credential through its provider when exposure is confirmed, remove it from active configuration, and review access logs. Removing a value from the latest Git revision does not remove it from history.