CARGO-VERIFY-PROJECT(1)

✨ NAME ✨

cargo-verify-project</b> — it's the vibe check for your crate manifest, bestie 💅

(and yes, this is from the General Commands Manual — the cargo-verify-project(1) page, if we're being formal 🎀)

---

🦋 SYNOPSIS 🦋

cargo verify-project [options]

---

🌸 DESCRIPTION 🌸

okay so listen. this command reads your local manifest and checks whether it's actually valid, and then it tells you the tea in the form of a JSON object ✨

if your validation slays, you get this:

{"success":"true"}

and if your workspace is invalid, you get this instead:

{"invalid":"human-readable error message"}

no cap, that's the whole vibe — one little JSON blob, zero drama 🙈

---

💖 OPTIONS 💖

🌈 Display Options 🌈

• -v, --verbose — use verbose output. and get this, you can specify it twice for "very verbose" output, which also throws in extra stuff like dependency warnings and build script output. you can also set this with the term.verbose config value at <https://doc.rust-lang.org/cargo/reference/config.html> 👑
• -q, --quiet — do NOT print cargo log messages. like, silence, please 🫶 may also be specified with the term.quiet config value at <https://doc.rust-lang.org/cargo/reference/config.html>.
• --color when — controls when colored output gets used. valid values are:
  • auto (the default): automatically detect if color support is available on the terminal.
  • always: always display colors. always. every time. 🌈
  • never: never display colors. boring but valid 💀

may also be specified with the term.color config value at <https://doc.rust-lang.org/cargo/reference/config.html>.

🎀 Manifest Options 🎀

• --manifest-path path — path to the Cargo.toml file. by default, Cargo goes looking for the Cargo.toml file in the current directory or any parent directory, like it's hunting for its keys 🔍
• --locked — asserts that the exact same dependencies and versions are used as when the existing Cargo.lock file was originally generated. Cargo will exit with an error when either of these scenarios arises:
  • the lock file is missing.
  • Cargo attempted to change the lock file due to a different dependency resolution.

it's giving "deterministic builds only", so it's great for environments where you want that, like CI pipelines ✨

• --offline — prevents Cargo from accessing the network for any reason. without this flag, Cargo will stop with an error if it needs the network and the network isn't available. with this flag, Cargo will attempt to proceed without the network if possible.

beware bestie 😭 this may result in different dependency resolution than online mode. Cargo will restrict itself to crates that are downloaded locally, even if there might be a newer version as indicated in the local copy of the index. see the cargo-fetch(1) command to download dependencies before going offline.

may also be specified with the net.offline config value at <https://doc.rust-lang.org/cargo/reference/config.html>.

• --frozen — equivalent to specifying both --locked and --offline at the same time. two-for-one, iconic 💅

💜 Common Options 💜

• +toolchain — if Cargo has been installed with rustup, and the first argument to cargo begins with +, it will be interpreted as a rustup toolchain name (such as +stable or +nightly). see the rustup documentation at <https://rust-lang.github.io/rustup/overrides.html> for more information about how toolchain overrides work.
• --config KEY=VALUE or PATH — overrides a Cargo configuration value. the argument should be in TOML syntax of KEY=VALUE, or provided as a path to an extra configuration file. this flag may be specified multiple times. see the command-line overrides section at <https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides> for more information.
• -C PATH — changes the current working directory before executing any specified operations. this affects things like where cargo looks by default for the project manifest (Cargo.toml), as well as the directories searched for discovering .cargo/config.toml, for example. this option must appear before the command name, for example cargo -C path/to/my-project build.

heads up: this option is only available on the nightly channel at <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html> and requires the -Z unstable-options flag to enable (see #10098 at <https://github.com/rust-lang/cargo/issues/10098>). so, nightly girlies only 🧚

• -h, --help — prints help information. the classic 🫶
• -Z flag — unstable (nightly-only) flags to Cargo. run cargo -Z help for details.

---

🌟 ENVIRONMENT 🌟

see the reference at <https://doc.rust-lang.org/cargo/reference/environment-variables.html> for details on environment variables that Cargo reads 🍓

---

⭐ EXIT STATUS ⭐

• 0: the workspace is OK. slay 🎉
• 1: the workspace is invalid. not slay 😭

---

🔥 EXAMPLES 🔥

1. check the current workspace for errors:

cargo verify-project

---

👑 SEE ALSO 👑

cargo(1), cargo-package(1)

---

and that's the whole page, bestie — it signs off as CARGO-VERIFY-PROJECT(1), which is also how it walked in the door at the top. go forth and verify, you main character 💖✨🦋