evidencectl target explain command reference
Inspect one normalized target and its complete grants.
Contract status
Section titled “Contract status”This page is generated from the public Clap command tree for Registry Stack source version 0.45.0 and catalog SHA-256 18546dbdf436972522108829ab0f8c804142a7474cfe3841e0b8ff10e061c842. Hidden implementation commands are omitted.
evidencectl target explain [OPTIONS] <TARGET> [PROJECT]Arguments
Section titled “Arguments”| Argument | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
<TARGET> | Yes | n/a | n/a | n/a | Normalized target.yaml, or a directory containing target.yaml |
[PROJECT] | No | . | n/a | n/a | Evidence project directory; defaults to the current directory. This command needs an editable project holding evidence.yaml. |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--json | No | n/a | n/a | n/a | Emit one machine-readable JSON report |
--format <FORMAT> | No | human | human, json, junit | n/a | Emit the selected command’s report in this format. junit is accepted only by test and fixtures run |
-h, --help | No | n/a | n/a | n/a | Print help (see a summary with ‘-h’) |
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.