[Home](/en/ai)

[Catalog](/en/ai/catalog)

What verification evidence proves and what it does not.

[Overview](/en/ai/docs)

[Quickstart](/en/ai/docs/quickstart)

[For people](/en/ai/docs/quickstart/human)

[For agents](/en/ai/docs/quickstart/agent)

[Catalog](/en/ai/docs/catalog)

[CLI](/en/ai/docs/cli)

[Overview](/en/ai/docs/trust-and-safety)

[Security checks](/en/ai/docs/security-checks)

[Troubleshooting](/en/ai/docs/troubleshooting)

# Security checks Inspect evidence for the exact artifact, target and policy. Author identity and component verification are independent. A passing scan is evidence within that check's scope, not a guarantee about every possible behavior. An unavailable scanner, timeout or malformed package is degraded execution, not a successful scan or a malware finding. Inapplicable checks do not run. The worker's current policy and result models define required checks; the UI displays those results. Follow the CLI's mechanical admission decision. Do not bypass failed compatibility, access, integrity or required-evidence checks. See [trust](trust-and-safety/index.md).