CARGO-INFO(1)

💖 NAME 💖

okay so bestie, this is cargo-info — it displays information about a package. that's the whole vibe. 🫶

---

✨ SYNOPSIS ✨

cargo info [options] spec

---

🌸 DESCRIPTION 🌸

so basically this command shows you the tea on a package. it goes and fetches the data from that package's Cargo.toml file and then presents it to you in a human-readable format. it's giving "tell me everything" energy and honestly? iconic. 💅

---

🎀 OPTIONS 🎀

🍓 Info Options

• spec — fetch the info about the package you specified. the spec can be a package ID, so peep cargo-pkgid(1) for the SPEC format (iykyk). if the package you named is part of the current workspace, you'll get the info straight from the local Cargo.toml file instead. also, if the Cargo.lock file doesn't exist yet, it will be created. and if you didn't specify a version, the appropriate version gets picked based on the Minimum Supported Rust Version (MSRV). no cap. ✨
• --index index — the URL of the registry index to use.
• --registry registry — the name of the registry to use. registry names are defined in Cargo config files: https://doc.rust-lang.org/cargo/reference/config.html. if you don't specify one, the default registry is used, which is defined by the registry.default config key, and that defaults to crates-io. slay.

🦋 Display Options

• -v, --verbose — use verbose output. you can specify it twice for "very verbose" output, which includes extra stuff like dependency warnings and build script output. may also be specified with the term.verbose config value: https://doc.rust-lang.org/cargo/reference/config.html.
• -q, --quiet — do not print cargo log messages. may also be specified with the term.quiet config value: https://doc.rust-lang.org/cargo/reference/config.html.
• --color when — controls when colored output is used. valid values are:
  • 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.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 arises:
  • the lock file is missing.
  • Cargo attempted to change the lock file due to a different dependency resolution.

it may be used in environments where deterministic builds are desired, such as in CI pipelines. very demure, very deterministic. 🎀

• --offline — prevents Cargo from accessing the network for any reason. without this flag, Cargo will stop with an error if it needs to access 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: https://doc.rust-lang.org/cargo/reference/config.html.

• --frozen — equivalent to specifying both --locked and --offline. two for one, we love a combo deal. 💅

🌈 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: 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: 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 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). nightly girlies only. 💀

• -h, --help — prints help information. our savior fr fr.
• -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. we ate. 👑
• 101: Cargo failed to complete. it's giving tragedy. 😭

---

🧚 EXAMPLES 🧚

1. inspect the serde package from crates.io:

cargo info serde

2. inspect the serde package with version 1.0.0:

cargo info serde@1.0.0

3. inspect the serde package from the local registry:

cargo info serde --registry my-registry

---

💖 SEE ALSO 💖

cargo(1), cargo-search(1)

---

and that's the whole page bestie!! this lil manual page is from CARGO-INFO(1) — General Commands Manual, dated CARGO-INFO(1) at the bottom, which honestly is just the title doing a little encore at the end. periodt. 💅✨