CLI reference
chock compliance
Ask the user before running chock compliance: what it takes and prints, from the engine at the pinned commit.
Generate a compliance coverage report (compliance report --framework owasp_asi)
Exit codes
- This command reads its arguments itself, without argparse.
- Chock documents no other exit codes. Each example below shows the code its run returned.
Examples
Real runs, recorded by python -m sitegen.cliexamples with the engine at the pinned commit. The steps of data/cli-examples.yaml ran in order, offline, in one fresh git repository at /work/demo (made with git init -b main), with HOME at /home/demo. Those paths stand for the throwaway folders the runs used, and <time> stands for a timestamp. Output is stdout and stderr together.
Step 16 of 21, exit code 0.
$ chock compliance report --repo .
Framework: owasp_asi
Control State Title / Covering policies
----------------------------------------------------------------------
ASI01 uncovered Agent Goal Hijack
ASI02 uncovered Tool Misuse & Exploitation
ASI03 uncovered Identity & Privilege Abuse
ASI04 uncovered Agentic Supply Chain
ASI05 uncovered Unexpected Code Execution
ASI06 uncovered Memory & Context Poisoning
ASI07 uncovered Insecure Inter-Agent Communication
ASI08 uncovered Cascading Failures
ASI09 uncovered Human-Agent Trust Exploitation
ASI10 uncovered Rogue Agents
Help as printed
This command reads its arguments itself, without argparse, so this is all the engine says about them: what it prints for --help.
Usage: chock compliance report [--repo .] [--framework owasp_asi] [--json]
Built from engine 5a4b6287a46e and catalog 1e60d211c1bb.