18 releases (7 breaking)

0.19.0 Jan 3, 2023
0.17.0 Dec 30, 2022
0.13.0 Nov 29, 2022
0.0.13 Jul 17, 2022
0.0.3 Dec 30, 2021

#813 in Command line utilities

Download history 14/week @ 2022-11-30 27/week @ 2022-12-07 15/week @ 2022-12-14 24/week @ 2022-12-21 83/week @ 2022-12-28 31/week @ 2023-01-04 12/week @ 2023-01-11 8/week @ 2023-01-18 7/week @ 2023-01-25 7/week @ 2023-02-01 26/week @ 2023-02-08 61/week @ 2023-02-15 1/week @ 2023-02-22 2/week @ 2023-03-01 37/week @ 2023-03-15

58 downloads per month

MIT license


Licensebat CLI

A tool to help you verify that your dependencies comply with your license policies.

Check the docs for more information.

license crates.io docs.rs

What is Licensebat?

Licensebat is a CLI that you can use for free to verify that the dependencies of your project follow your license policies.

Let's say, for instance, that you are building a proprietary application. In that case, you may consider avoiding the use of some software with a restrictive license like GPL.

By using Licensebat, you can check you don't have any dependency with such a restrictive license. Normally, it will look in all the the dependency tree of your project, so transient dependencies will also be considered.

Feel free to use the CLI in your CI/CD pipeline, or in your continuous integration server.

Important: licensebat-cli is still in development so you may use it at your own risk.

Licensebat GitHub App

Aside from the CLI, Licensebat can be used directly in your GitHub repositories by installing this GitHub App.

Supported languages

Crates.io Crates.io Crates.io

How to use it

Just run this:

licensebat --dependency-file ./Cargo.lock

That will set all in motion. Take into account that you'll need to have access to the internet for the cli to work properly.

You can have more information about the CLI by running licensebat --help.

licensebat [OPTIONS] --dependency-file <dependency-file>
    -h, --help       Prints help information
    -V, --version    Prints version information
    -d, --dependency-file <dependency-file>    Path to the file containing the dependencies of the project. i.e.
                                               package-lock.json for npm projects, yarn.lock for yarn projects, etc
    -l, --licrc-file <licrc-file>              Path to the .licrc file [default: .licrc]

The .licrc file

But before running, you have to be sure you have a .licrc file available in your project.

You can get a copy from this gist. It's a TOML file with configuration about which are the accepted or denied licenses, ignored dependencies or whether to block or not the PR (exit code == 1) in case it finds invalid dependencies.

# This indicates which are the only licenses that Licensebat will accept.
# The rest will be flagged as not allowed.
accepted = ["MIT", "MSC", "BSD"]
# This will indicate which licenses are not accepted.
# The rest will be accepted, except for the unknown licenses or dependencies without licenses.
# unaccepted = ["LGPL"]
# Note that only one of the previous options can be enabled at once.
# If both of them are informed, only accepted will be considered.

# This will allow users to flag some dependencies so that Licensebat will not check for their license.
ignored=["ignored_dep1", "ignored_dep2"]

# False by default (always exit code == 0), if true, it will exit with code 1 in case some invalid dependency is found.
do_not_block_pr = false


Licensebat uses tracing. You can get logs while running the CLI by setting the RUST_LOG environment variable.

RUST_LOG=licensebat=info cargo run --dependency-file ./Cargo.lock


~516K SLoC