cargo verify-project
NAME
cargo-verify-project - Check correctness of crate manifest
SYNOPSIS
cargo verify-project [OPTIONS]
DESCRIPTION
This command will parse the local manifest and check its validity. It emits a JSON object with the result. A successful validation will display:
{"success":"true"}
An invalid workspace will display:
{"invalid":"human-readable error message"}
OPTIONS
Display Options
- -v
- --verbose
-
Use verbose output. May be specified twice for "very verbose" output which includes extra output such as dependency warnings and build script output. May also be specified with the
term.verboseconfig value. - -q
- --quiet
-
No output printed to stdout.
- --color WHEN
-
Control when colored output is used. Valid values:
-
auto(default): Automatically detect if color support is available on the terminal. -
always: Always display colors. -
never: Never display colors.
May also be specified with the
term.colorconfig value. -
Manifest Options
- --manifest-path PATH
-
Path to the
Cargo.tomlfile. By default, Cargo searches in the current directory or any parent directory for theCargo.tomlfile. - --frozen
- --locked
-
Either of these flags requires that the
Cargo.lockfile is up-to-date. If the lock file is missing, or it needs to be updated, Cargo will exit with an error. The--frozenflag also prevents Cargo from attempting to access the network to determine if it is out-of-date.These may be used in environments where you want to assert that the
Cargo.lockfile is up-to-date (such as a CI build) or want to avoid network access.
Common Options
- -h
- --help
-
Prints help information.
- -Z FLAG…
-
Unstable (nightly-only) flags to Cargo. Run
cargo -Z helpfor details.
ENVIRONMENT
See the reference for details on environment variables that Cargo reads.
Exit Status
- 0
-
The workspace is OK.
- 1
-
The workspace is invalid.
EXAMPLES
-
Check the current workspace for errors:
cargo verify-project