CARGO-REPORT(1)

🌸 CARGO-REPORT(1) 🌸

okay bestie, welcome to the General Commands Manual page for cargo-report — yes, the manual name is literally General Commands Manual, and this whole thing lives under it. let's get into it 💅

---

✨ NAME ✨

cargo-report — Generate and display various kinds of reports 🎀

---

✨ SYNOPSIS ✨

cargo report type [options]

---

✨ DESCRIPTION ✨

It shows you a report of whatever type you asked for — and right now, the only type on the menu is future-incompat. that's it, that's the whole vibe. only future-incompat is supported. periodt ✨

---

✨ OPTIONS ✨

💖 Display Options 💖

• -v, --verbose — bestie wants the verbose output. say it twice and you get "very verbose" mode, which is the one that also throws in extra stuff like dependency warnings and build script output 👀. you can also just set this with the term.verbose config value (<https://doc.rust-lang.org/cargo/reference/config.html>).
• -q, --quiet — do NOT print cargo log messages, we're being chill 😌. you can also set this with the term.quiet config value (<https://doc.rust-lang.org/cargo/reference/config.html>).
• --color when — controls when colored output happens. the valid values are:
  • auto (this is the default): automatically detect if the terminal supports color. it figures out the vibe check itself 🦋
  • always: always show colors. rainbow mode, no cap 🌈
  • never: never show colors. monochrome era 💀

you can also set this with the term.color config value (<https://doc.rust-lang.org/cargo/reference/config.html>).

💖 Manifest Options 💖

• --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 shows up:
  • the lock file is missing 😭
  • cargo attempted to change the lock file because of a different dependency resolution

it's giving deterministic builds, so use it in 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 try to proceed without the network if it can 🌙

beware bestie — this may result in a 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.

you can also set this with the net.offline config value (<https://doc.rust-lang.org/cargo/reference/config.html>).

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

💖 Common Options 💖

• +toolchain — if cargo was installed with rustup, and the first argument to cargo begins with +, it gets interpreted as a rustup toolchain name (like +stable or +nightly). see the rustup documentation (<https://rust-lang.github.io/rustup/overrides.html>) for more info on 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 given as a path to an extra configuration file. this flag may be specified multiple times ✨. see the command-line overrides section (<https://doc.rust-lang.org/cargo/reference/config.html#command-line-overrides>) for more info.
• -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), and also the directories searched for discovering .cargo/config.toml, for example. this option must appear before the command name, like cargo -C path/to/my-project build 👈

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

• -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 (<https://doc.rust-lang.org/cargo/reference/environment-variables.html>) for details on environment variables that cargo reads 🌱

---

✨ EXIT STATUS ✨

• 0: cargo succeeded 🎉
• 101: cargo failed to complete 😭

---

✨ EXAMPLES ✨

1. Display the available kinds of reports:

cargo report --help

---

✨ SEE ALSO ✨

cargo(1), cargo-report-future-incompatibilities(1)

---

and that's the whole page, bestie 🫶 this was CARGO-REPORT(1) from the General Commands Manual, version/date line reading CARGO-REPORT(1) — slay, go forth and generate those reports 💖✨🌸