evidencectl keygen command reference
Generate Registry Evidence deployment key material as owner-only files.
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 keygen [OPTIONS] <COMMAND>Commands
Section titled “Commands”| Command | Description |
|---|---|
signing | P-256 ES256 signing keypair as private and public JWK files |
secret | One random raw secret file, 32 bytes (audit or subject-binding HMAC) |
token | One random bearer token file, printable and header-safe |
holder | P-256 ES256 holder keypair for SD-JWT VC confirmation binding |
client-assertion | Keypair a source’s clientAssertionKeyRef points at, for a token endpoint that authenticates the client by signed assertion |
Options
Section titled “Options”| Option | Always required | Default | Values | Environment | Description |
|---|---|---|---|---|---|
--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 |
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.