Need help with cargo-about?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

188 Stars 10 Forks Other 105 Commits 11 Opened issues


📜 Cargo plugin to generate list of all licenses for a crate 🦀

Services available


Need anything else?

Contributors list

📜 cargo-about

Embark Embark Docs dependency status Build Status

Cargo plugin for generating a listing of all of the crates used by a root crate, and the terms under which they are licensed.

Please Note: This is a tool that we use (and like!) and it makes sense to us to release it as open source. However, we can’t take any responsibility for your use of the tool, if it will function correctly or fulfil your needs. No functionality in - or information provided by - cargo-about constitutes legal advice.

Getting started



cargo install cargo-about

From the AUR

Arch Linux users can install cargo-about from the AUR using an AUR helper. For example,

paru -S cargo-about

Generate license information for your own project

# Generates `about.toml` and `about.hbs` in your cargo project
cargo about init
# Generate the license information with
cargo about generate about.hbs > license.html



Priority list of all the accepted licenses for a project.

will try to satisfy the licenses in the order that they are declared in this list.
accepted = [


A list of targets that are actually building for. Crates which are only included via

expressions that don't match one or more of the listed targets will be ignored.
targets = [


If true, all crates that are only used as build dependencies will be ignored.

ignore-build-dependencies = true


If true, all crates that are only used as dev dependencies will be ignored.

ignore-dev-dependencies = true


  • root
    Name of the root folder
  • license
    Name of the license. Has to be parsable from SPDX, see
  • license-file
    The path to the license file where the license is specified
  • license-start
    The starting line number of the license in the specified license file
  • license-end
    The ending line number of the license in the specified license file
# Example
root = "PhysX"
license = "BSD-3-Clause"
license-file = "PhysX/"
license-start = 3
license-end = 28


Sometimes libraries include licenses for example code that you don't want to use.

  • license
    Name of the license that you want to ingore. Has to be parsable from SPDX, see
  • license-file
    The path to the license file where the license is specified
license = "Zlib"
license-file = "third-party/cimgui/imgui/examples/libs/glfw/COPYING.txt"


See handlebars


  • overview
    A list of
  • licenses
    A list of



  • count
    The number of times the license is used
  • name
    The name of the license
  • id
    of the license


  • name
    The full name of the license
  • id
    The SPDX identifier
  • text
    The license text
  • source_path
    The path of the license
  • used_by
    A list of


  • crate
    Metadata for a cargo package
  • path
    Optional path of the dependency that is being used by the license


    {{#each overview}}
  • {{name}} ({{count}})
  • {{/each}}

Preview of the default

license You can view the full license here


Unable to satisfy the following licenses

[ERROR] Crate 'aho-corasick': Unable to satisfy [Unlicense OR MIT], with the following accepted licenses [Apache-2.0]

In this case you are missing either

as an
license in your


Contributor Covenant

We welcome community contributions to this project.

Please read our Contributor Guide for more information on how to get started.


Licensed under either of

  • Apache License, Version 2.0, (LICENSE-APACHE or
  • MIT license (LICENSE-MIT or

at your option.


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

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.