Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

cpplint review

Free#30 of 33 in Linters

A focused, configurable choice for C++ teams applying Google's style guide.

6.2/10Editor score
cpplint6.2 Visit cpplint

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

cpplint is an open-source command-line linter for C and C++ source files. It is aimed at teams that want automated checks aligned with Google's C++ style guide, covering build, readability, runtime, and whitespace categories. Recursive file discovery, customizable file extensions, exclusion patterns, and per-directory CPPLINT.cfg files help teams apply consistent checks across source trees. NOLINT comments and blocks provide targeted suppression when a reported issue is intentional.

The published project model is open-source distribution rather than commercial plan tiers. Its configuration is practical for repository-based workflows: teams can select category filters, define which files are scanned, exclude paths, and choose output formats including JUnit, Eclipse, Visual Studio, sed, and gsed. The sed-compatible output supports some fixes, while pre-commit hook support can place checks before changes enter a repository. These options make cpplint suitable for teams that prefer a lightweight command-line tool and configurable style enforcement over a broader analysis platform.

Its ecosystem fit is strongest in pre-commit and continuous-integration workflows. cpplint supports CI on GitHub and integrates with pre-commit and MegaLinter, giving teams established automation points without changing its focused command-line approach. The trade-off is scope: the published specifications show support for two languages, no verified custom rules, no security rules, and no native IDE support. Teams following Google's conventions and comfortable with repository or CI-based checks should find a clear fit; teams needing security analysis, custom rule authoring, or editor-integrated feedback should choose a broader linter instead.

cpplint pros and cons

  • Where it wins
    • Checks C and C++ against Google's C++ style guide
    • Configures filters, exclusions, extensions, and per-directory settings
    • Supports pre-commit, CI, and multiple machine-readable output formats
  • Where it doesn't
    • No verified custom rules or security rules
    • No native IDE support
    • Focused on C and C++ style and code-quality checks

cpplint fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update