Skip to content
Registry StackDocsv0.46.0

evidencectl command reference

View as Markdown

Evidence adopter tooling: keys, source authoring, fixture runs.

This page is generated from the public Clap command tree for Registry Stack source version 0.46.0 and catalog SHA-256 d43b1bf418e0b00fac52311fa3a106fa124512dbc88cf511475713af2d73aa47. Hidden implementation commands are omitted.

evidencectl [OPTIONS] <COMMAND>
CommandDescription
apiSend one raw HTTP request to a configured or ready local Evidence service
initCreate a new editable Evidence project
typesGenerate typed project outputs and Requirement URI names
checkCheck a normalized project and, when selected, deployment closure, or one tooling file, offline
explainExplain the authored inventory and optional target-owned governance
testRun the project’s synthetic Evidence fixtures
packageCompile an editable project into a reviewed deployment candidate
generateGenerate configuration documents for other tools from this product’s configuration
accessManage target access profiles and local caller clients
keygenGenerate Registry Evidence deployment key material as owner-only files
jwksAssemble a public JWKS document from public JWK files
jwkConvert public key material into a public JWK
fixturesDrive the evidence binary across a project’s bundle fixtures
doctorCheck one runtime configuration and its startup dependencies
artifactInspect deployment artifact custody
devRun the private local issuer and Registry Evidence pair
oid4vciOperate the optional Evidence wallet-delivery service
auditInspect stopped local audit history
connectionManage named Evidence API connections
clientConfigure progressive relying-party clients and fetch contract candidates
sourceWork with a project’s sources, starting from their own API documents
targetCreate and inspect complete deployment targets
requestPrepare a closed request for the active local project
verifyVerify one retained Registry Evidence response offline
toolingAdvanced: editor and tooling integration surfaces
runtimeRun the matching Evidence runtime with unchanged arguments and streams; use runtime -- --help for its native command tree
OptionAlways requiredDefaultValuesEnvironmentDescription
--format <FORMAT>Nohumanhuman, json, junitn/aEmit the selected command’s report in this format. junit is accepted only by test and fixtures run
-h, --helpNon/an/an/aPrint help
-V, --versionNon/an/an/aPrint version

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.