Overview
A map of the openvet CLI: which subcommand to reach for, when.
The openvet CLI groups roughly into three jobs.
Consuming audits #
These are the commands you’ll run in a project that depends on third-party packages.
openvet init— write a starteropenvet.tomlinto the current directory.openvet update— fetch trusted logs, verify them, and pin the heads intoopenvet.lock.openvet check— verify your lockfile satisfies the policy inopenvet.toml. Run this in CI.
Authoring and publishing audits #
For when you want to record your own review of a package and make it available for others (or your future self) to consume.
openvet audit— the authoring family:audit new,audit edit,audit sign,audit publish.
TODO: cover key management (
openvet key) and log operator commands once their pages are written.