Skip to content
This repository has been archived by the owner. It is now read-only.
Branch: master
Go to file

Latest commit


Failed to load latest commit information.
Latest commit message
Commit time


Note: This crate is moving into upstream Cargo itself. If you're on the nightly channel as of 2019-06-20 you don't need to install cargo-vendor, but rather cargo vendor just works.

All future development of a vendor subcommand will happen in upstream Cargo itself, and issues/bugs should not be reported to this repository any more.

In other words this project is DEPRECATED since it's moved into Cargo.

Build Status Build status

This is a Cargo subcommand which vendors all dependencies into a local directory using Cargo's support for source replacement.


Currently this can be installed with:

$ cargo install cargo-vendor

You can also install precompiled binaries that are assembled on the CI for this crate.

Example Usage

Simply run cargo vendor inside of any Cargo project:

$ cargo vendor
add this to your .cargo/config for this project:

    replace-with = 'vendored-sources'

    directory = '/home/alex/code/cargo-vendor/vendor'

This will populate the vendor directory which contains the source of all dependencies. When configured, Cargo will then use this directory instead of looking at

Also note that the output of cargo vendor that should be configuration is all on stdout (as opposed to stderr where other messages go), so you can also do:

$ cargo vendor > .cargo/config

to vendor and initialize your config in the same step!

Flag --no-merge-sources

If the vendored Cargo project makes use of [replace] sections it can happen that the vendoring operation fails, e.g. with an error like this:

found duplicate version of package `libc v0.2.43` vendored from two sources:

The flag --no-merge-sources should be able to solve that. Make sure to grab the .cargo/config file directly from standard output since the config gets more complicated and unpredictable.


$ cargo vendor --no-merge-sources > .cargo/config


This project is licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in cargo-vendor by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

You can’t perform that action at this time.