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

About the developer

5.8K Stars 813 Forks Other 11.7K Commits 1.1K Opened issues


A bunch of lints to catch common mistakes and improve your Rust code

Services available


Need anything else?

Contributors list


Clippy Test License: MIT OR Apache-2.0

A collection of lints to catch common mistakes and improve your Rust code.

There are over 450 lints included in this crate!

Lints are divided into categories, each with a default lint level. You can choose how much Clippy is supposed to ~~annoy~~ help you by changing the lint level by category.

| Category | Description | Default level | | --------------------- | ----------------------------------------------------------------------- | ------------- | |

| all lints that are on by default (correctness, style, complexity, perf) | warn/deny | |
| code that is outright wrong or very useless | deny | |
| code that should be written in a more idiomatic way | warn | |
| code that does something simple but in a complex way | warn | |
| code that can be written to run faster | warn | |
| lints which are rather strict or might have false positives | allow | |
| new lints that are still under development | allow | |
| lints for the cargo manifest | allow |

More to come, please file an issue if you have ideas!

The lint list also contains "restriction lints", which are for things which are usually not considered "bad", but may be useful to turn on in specific cases. These should be used very selectively, if at all.

Table of contents:


Below are instructions on how to use Clippy as a subcommand, compiled from source or in Travis CI.

As a cargo subcommand (
cargo clippy

One way to use Clippy is by installing Clippy through rustup as a cargo subcommand.

Step 1: Install rustup

You can install rustup on supported platforms. This will help us install Clippy and its dependencies.

If you already have rustup installed, update to ensure you have the latest rustup and compiler:

rustup update

Step 2: Install Clippy

Once you have rustup and the latest stable release (at least Rust 1.29) installed, run the following command:

rustup component add clippy

If it says that it can't find the

component, please run
rustup self update

Step 3: Run Clippy

Now you can run Clippy by invoking the following command:

cargo clippy

Automatically applying Clippy suggestions

Clippy can automatically apply some lint suggestions. Note that this is still experimental and only supported on the nightly channel:

cargo clippy --fix -Z unstable-options


All the usual workspace options should work with Clippy. For example the following command will run Clippy on the

cargo clippy -p example

As with

cargo check
, this includes dependencies that are members of the workspace, like path dependencies. If you want to run Clippy only on the given crate, use the
option like this:
cargo clippy -p example -- --no-deps 

As a rustc replacement (

Clippy can also be used in projects that do not use cargo. To do so, you will need to replace your

compilation commands with
. For example, if your project runs:
rustc --edition 2018 -Cpanic=abort

Then, to enable Clippy, you will need to call:

clippy-driver --edition 2018 -Cpanic=abort

Note that

will still run, i.e. it will still emit the output files it normally does.

Travis CI

You can add Clippy to Travis CI in the same way you use it locally:

language: rust
  - stable
  - beta
  - rustup component add clippy
  - cargo clippy
  # if you want the build job to fail when encountering warnings, use
  - cargo clippy -- -D warnings
  # in order to also check tests and non-default crate features, use
  - cargo clippy --all-targets --all-features -- -D warnings
  - cargo test
  # etc.

Note that adding

-D warnings
will cause your build to fail if any warnings are found in your code. That includes warnings found by rustc (e.g.
, etc.). If you want to avoid this and only cause an error for Clippy warnings, use
in your code or
-D clippy::all
on the command line. (You can swap
with the specific lint category you are targeting.)


Some lints can be configured in a TOML file named

. It contains a basic
variable =
mapping eg.
blacklisted-names = ["toto", "tata", "titi"]
cognitive-complexity-threshold = 30

See the list of lints for more information about which lints can be configured and the meaning of the variables.

To deactivate the “for further information visit lint-link” message you can define the

environment variable.

Allowing/denying lints

You can add options to your code to

Clippy lints:
  • the whole set of

    lints using the
    lint group (
  • all lints using both the

    lint groups (
    ). Note that
    contains some very aggressive lints prone to false positives.
  • only some lints (

    #![deny(clippy::single_match, clippy::box_vec)]
    , etc.)
  • allow
    can be limited to a single function or module using
    , etc.


means to suppress the lint for your code. With
the lint will only emit a warning, while with
the lint will emit an error, when triggering for your code. An error causes clippy to exit with an error code, so is useful in scripts like CI/CD.

If you do not want to include your lint levels in your code, you can globally enable/disable lints by passing extra flags to Clippy during the run:

To allow

, run
cargo clippy -- -A clippy::lint_name

And to warn on

, run
cargo clippy -- -W clippy::lint_name

This also works with lint groups. For example you can run Clippy with warnings for all lints enabled:

cargo clippy -- -W clippy::pedantic

If you care only about a single lint, you can allow all others and then explicitly warn on the lint(s) you are interested in:

cargo clippy -- -A clippy::all -W clippy::useless_format -W clippy::...

Specifying the minimum supported Rust version

Projects that intend to support old versions of Rust can disable lints pertaining to newer features by specifying the minimum supported Rust version (MSRV) in the clippy configuration file.

msrv = "1.30.0"

The MSRV can also be specified as an inner attribute, like below.

#![clippy::msrv = "1.30.0"]

fn main() { ... }

You can also omit the patch version when specifying the MSRV, so

msrv = 1.30
is equivalent to
msrv = 1.30.0


is an unstable feature so it has to be enabled explicitly.

Lints that recognize this configuration option can be found here


If you want to contribute to Clippy, you can find more information in


Copyright 2014-2020 The Rust Project Developers

Licensed under the Apache License, Version 2.0 or the MIT license , at your option. Files in the project may not be copied, modified, or distributed except according to those terms.

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.