evidencectl verify command reference
Verify one retained Registry Evidence response offline.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.46.1 and catalog SHA-256 61bebbb88fe15e4da92e2b0adbca0cd5b1a47b8eac38f4b91a15095011368a43. Hidden implementation commands are omitted.
evidencectl verify [OPTIONS] --context <CONTEXT> --output <OUTPUT> <RESPONSE>Arguments
Section titled “Arguments”| Argument | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
<RESPONSE> | Yes | n/a | n/a | n/a | Signed JWS or SD-JWT VC response returned by Registry Evidence |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--context <CONTEXT> | Yes | n/a | n/a | n/a | Owner-only verification context retained before the response existed |
--output <OUTPUT> | Yes | n/a | n/a | n/a | New owner-only file for the exact verified Registry Evidence payload |
--format <FORMAT> | No | human | human | n/a | Select human-readable output; this command provides no JSON report |
-h, --help | No | n/a | n/a | n/a | Print help |
Generation contract
Section titled “Generation contract”After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.