cargo-vendor - Vendor all dependencies locally
cargo vendor [OPTIONS] [PATH]
This cargo subcommand will vendor all crates.io and git dependencies for a
project into the specified directory at
<path>. After this command completes
the vendor directory specified by
<path> will contain all remote sources from
dependencies specified. Additional manifests beyond the default one can be
specified with the
cargo vendor command will also print out the configuration necessary
to use the vendored sources, which you will need to add to
- -s MANIFEST
- --sync MANIFEST
Cargo.tomlmanifests to workspaces which should also be vendored and synced to the output.
Don’t delete the "vendor" directory when vendoring, but rather keep all existing contents of the vendor directory
Instead of ignoring
[source]configuration by default in
.cargo/configread it and use it when downloading crates from crates.io, for example
Normally versions are only added to disambiguate multiple versions of the same package. This option causes all directories in the "vendor" directory to be versioned, which makes it easier to track the history of vendored packages over time, and can help with the performance of re-vendoring when only a subset of the packages have changed.
- --manifest-path PATH
Path to the
Cargo.tomlfile. By default, Cargo searches for the
Cargo.tomlfile in the current directory or any parent directory.
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
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
Prints help information.
- -Z FLAG…
Unstable (nightly-only) flags to Cargo. Run
cargo -Z helpfor details.
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.
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 is not available. With this flag, Cargo will attempt to proceed without the network if possible.
Beware that 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
See the reference for details on environment variables that Cargo reads.
Cargo failed to complete.
Vendor all dependencies into a local "vendor" folder
Vendor all dependencies into a local "third-party/vendor" folder
cargo vendor third-party/vendor
Vendor the current workspace as well as another to "vendor"
cargo vendor -s ../path/to/Cargo.toml