Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Wednesday, July 27, 2022

cargo-vendor (1)


cargo-vendor - Vendor all dependencies locally


cargo vendor [options] [path]


CARGO-VENDOR(1)             General Commands Manual            CARGO-VENDOR(1)

       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 -s option.

       The cargo vendor command will also print out the configuration
       necessary to use the vendored sources, which you will need to add to

   Vendor Options
       -s manifest, --sync manifest
           Specify extra Cargo.toml manifests 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/config.toml read 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

   Manifest Options
       --manifest-path path
           Path to the Cargo.toml file. By default, Cargo searches for the
           Cargo.toml file in the current directory or any parent directory.

       --frozen, --locked
           Either of these flags requires that the Cargo.lock file is
           up-to-date. If the lock file is missing, or it needs to be updated,
           Cargo will exit with an error. The --frozen flag also prevents
           Cargo from attempting to access the network to determine if it is

           These may be used in environments where you want to assert that the
           Cargo.lock file 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 net.offline config value

   Display Options
       -v, --verbose
           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 term.verbose
           config value

       -q, --quiet
           No output printed to stdout.

       --color when
           Control when colored output is used. Valid values:

           o  auto (default): Automatically detect if color support is
               available on the terminal.

           o  always: Always display colors.

           o  never: Never display colors.

           May also be specified with the term.color config value

   Common Options
           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.

       -h, --help
           Prints help information.

       -Z flag
           Unstable (nightly-only) flags to Cargo. Run cargo -Z help for

       See the reference
       for details on environment variables that Cargo reads.

       o  0: Cargo succeeded.

       o  101: Cargo failed to complete.

        1. Vendor all dependencies into a local "vendor" folder

               cargo vendor

        2. Vendor all dependencies into a local "third-party/vendor" folder

               cargo vendor third-party/vendor

        3. Vendor the current workspace as well as another to "vendor"

               cargo vendor -s ../path/to/Cargo.toml

       See attributes(7) for descriptions of the following attributes:

       |Availability   | developer/rust/cargo |
       |Stability      | Volatile             |


       Source code for open source software components in Oracle Solaris can
       be found at https://www.oracle.com/downloads/opensource/solaris-source-

       This software was built from source available at
       https://github.com/oracle/solaris-userland. The original community
       source was downloaded from  https://static.rust-

       Further information about this software can be found on the open source
       community website at http://www.rust-lang.org/.