LinthelmIntroductions to linters, static analysis and code-quality tools

Linters

What is Clippy? An introduction to the Rust Project's collection of Rust lints

By the Linthelm editorial team · Published · Updated

Clippy is a collection of lints for Rust. It catches common mistakes and helps improve Rust code, and it includes over 800 lints. It is installed through rustup and used as a cargo subcommand.

Tool
Clippy
Made by
Rust Project
Official site
github.com/rust-lang/rust-clippy
Category
Linters

Who makes Clippy

Clippy is made by the Rust Project. The official website is the rust-clippy repository on GitHub, linked below.

The tool is dual-licensed under Apache 2.0 and MIT.

Official website: github.com/rust-lang/rust-clippy

What Clippy is for

Clippy exists to catch mistakes and improve Rust code. Instead of a single checker with one fixed opinion, it ships as a collection of more than 800 lints, each looking for a specific problem or improvement opportunity.

The lints are grouped into categories, and each category has a default lint level. This means a project gets sensible behavior out of the box, while still being able to decide which groups to turn up or down.

Clippy can also apply some of its lint suggestions automatically. That turns part of the review feedback into changes you can accept directly rather than rewrite by hand.

Who Clippy is for

The vendor does not state a target audience, but the facts point to Rust developers who want automated feedback on their code. Clippy is installed through rustup and used as a cargo subcommand, so it suits projects that already use cargo.

It also works for projects that do not use cargo, through clippy-driver. Teams that run automated checks can add it to CI, and the documentation shows Travis CI as an example.

Notable capabilities

Clippy's feature set centers on controlling which lints run and where. The points below cover the main ways to shape its behavior.

  • Over 800 lints, grouped into categories that each have a default lint level.
  • Installation through rustup and use as a cargo subcommand.
  • Automatic application of some lint suggestions.
  • Use outside cargo projects through clippy-driver.
  • CI integration, with Travis CI shown as an example.
  • Lint levels limited to a single function or module with attributes.
  • Configuration of some lints through a clippy.toml file, including a minimum supported Rust version that disables lints about newer features.
  • The --no-deps option, which limits checking to the given crate and skips workspace dependencies.

How Clippy fits linters

Within the linters category, Clippy is a language-specific tool: its lints are written for Rust code and aim to catch mistakes and improve it. Its category system is where much of the practical tuning happens. The pedantic group contains aggressive lints that are prone to false positives, so it suits teams willing to review noisy results. The restriction category is not meant to be enabled as a whole, so lints there are better picked individually.

In Linthelm's wider niche of linters, static analysis and code quality, Clippy represents the approach of a rule collection with adjustable severity. Attributes allow scoping a lint level to one function or module, and clippy.toml lets a project record its settings alongside its code. Together these make it possible to adopt Clippy gradually and keep the rule set predictable across a team and its CI runs.

Frequently asked questions

What is Clippy used for?

Clippy is used to catch common mistakes and improve Rust code. It is a collection of over 800 lints grouped into categories.

Who develops Clippy?

Clippy is made by the Rust Project, and its official website is the rust-clippy repository on GitHub. It is dual-licensed under Apache 2.0 and MIT.

Can Clippy be used without cargo?

Yes. Projects that do not use cargo can run it through clippy-driver.

Can Clippy fix problems automatically?

It can automatically apply some lint suggestions, though not every lint offers one.

How do I limit Clippy to my own crate?

Use the --no-deps option, which limits Clippy to the given crate and skips workspace dependencies.

Sources. This introduction is based on the vendor's official pages, checked on 21 November 2026 (Asia/Dhaka):

Linthelm is independent and is not affiliated with Rust Project. Product names belong to their owners. Features change; confirm details on the official website.