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

yamllint review

Free#28 of 33 in Linters

A focused, configurable YAML linter for repositories, editors, hooks, and CI.

6.4/10Editor score
yamllint6.4 Visit yamllint

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

yamllint is an open-source command-line linter and Python module for YAML files. It is designed for teams maintaining YAML configuration and CI repositories, with checks covering syntax, formatting, indentation, comments, quoting, document markers, truthy values, line length, trailing spaces, and duplicate keys. Recursive directory linting helps apply checks across repository structures, while configurable YAML files let teams enable, disable, or tune rules for their workflow.

The published offering is free and open source rather than divided into paid tiers. Its workflow coverage is a central strength: yamllint supports machine-readable and editor-oriented output, pre-commit integration, GitHub Actions, GitLab CI/CD, and Arcanist. Editor integrations cover Vim, Neovim, Emacs, Visual Studio Code, and IntelliJ. It can also be used programmatically through its Python module, making it suitable for repository checks that need to run from scripts or CI pipelines. The listed platforms are Linux, macOS, and API access.

yamllint is a strong fit when the main requirement is consistent YAML syntax and style enforcement across local editing and automated checks. Its scope is deliberately focused: the published capabilities do not include autofix, custom rules, or security rules. Teams that want configurable formatting and duplicate-key detection without a paid plan should find the feature set well aligned with repository maintenance. Teams seeking automatic repairs, organization-specific rule extensions, or security-focused analysis should choose a linter that provides those capabilities instead.

yamllint pros and cons

  • Where it wins
    • Checks YAML syntax, style issues, and duplicate keys
    • Integrates with pre-commit, GitHub Actions, and GitLab CI/CD
    • Offers editor output, recursive linting, and Python module access
  • Where it doesn't
    • No autofix capability
    • No custom rule support
    • No security rules

yamllint 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