1CARGO-VERIFY-PROJECT(1) General Commands Manual CARGO-VERIFY-PROJECT(1)
2
6 cargo-verify-project - Check correctness of crate manifest
7
9 cargo verify-project [options]
10
12 This command will parse the local manifest and check its validity. It
13 emits a JSON object with the result. A successful validation will
14 display:
15 {"success":"true"}
17 An invalid workspace will display:
19 {"invalid":"human-readable error message"}
21
23 Display Options
24 -v, --verbose
25 Use verbose output. May be specified twice for "very verbose"
26 output which includes extra output such as dependency warnings and
27 build script output. May also be specified with the term.verbose
28 config value
29 <https://doc.rust-lang.org/cargo/reference/config.html>.
30 -q, --quiet
32 Do not print cargo log messages. May also be specified with the
33 term.quiet config value
34 <https://doc.rust-lang.org/cargo/reference/config.html>.
35 --color when
37 Control when colored output is used. Valid values:
38 • auto (default): Automatically detect if color support is
40 available on the terminal.
41 • always: Always display colors.
43 • never: Never display colors.
45 May also be specified with the term.color config value
47 <https://doc.rust-lang.org/cargo/reference/config.html>.
48 Manifest Options
50 --manifest-path path
51 Path to the Cargo.toml file. By default, Cargo searches for the
52 Cargo.toml file in the current directory or any parent directory.
53 --frozen, --locked
55 Either of these flags requires that the Cargo.lock file is
56 up-to-date. If the lock file is missing, or it needs to be updated,
57 Cargo will exit with an error. The --frozen flag also prevents
58 Cargo from attempting to access the network to determine if it is
59 out-of-date.
60 These may be used in environments where you want to assert that the
62 Cargo.lock file is up-to-date (such as a CI build) or want to avoid
63 network access.
64 --offline
66 Prevents Cargo from accessing the network for any reason. Without
67 this flag, Cargo will stop with an error if it needs to access the
68 network and the network is not available. With this flag, Cargo
69 will attempt to proceed without the network if possible.
70 Beware that this may result in different dependency resolution than
72 online mode. Cargo will restrict itself to crates that are
73 downloaded locally, even if there might be a newer version as
74 indicated in the local copy of the index. See the cargo-fetch(1)
75 command to download dependencies before going offline.
76 May also be specified with the net.offline config value
78 <https://doc.rust-lang.org/cargo/reference/config.html>.
79 Common Options
81 +toolchain
82 If Cargo has been installed with rustup, and the first argument to
83 cargo begins with +, it will be interpreted as a rustup toolchain
84 name (such as +stable or +nightly). See the rustup documentation
85 <https://rust-lang.github.io/rustup/overrides.html> for more
86 information about how toolchain overrides work.
87 --config KEY=VALUE or PATH
89 Overrides a Cargo configuration value. The argument should be in
90 TOML syntax of KEY=VALUE, or provided as a path to an extra
91 configuration file. This flag may be specified multiple times. See
92 the command-line overrides section
93 <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides>
94 for more information.
95 -h, --help
97 Prints help information.
98 -Z flag
100 Unstable (nightly-only) flags to Cargo. Run cargo -Z help for
101 details.
102
104 See the reference
105 <https://doc.rust-lang.org/cargo/reference/environment-variables.html>
106 for details on environment variables that Cargo reads.
107
109 • 0: The workspace is OK.
110 • 1: The workspace is invalid.
112
114 1. Check the current workspace for errors:
115 cargo verify-project
117
119 cargo(1), cargo-package(1)
120 CARGO-VERIFY-PROJECT(1)