LinthelmIntroductions to linters, static analysis and code-quality tools

Linters · 6 tools

Top 6 linting and formatting tools for YAML, TOML and config files

By the Linthelm editorial team · Published · Updated · Facts checked 21 November 2026 (Asia/Dhaka)

For config-heavy repos, start with yamllint for YAML, Taplo for TOML and dprint as a single formatter that covers several file types. This shortlist is for platform and DevOps engineers who need config files to stay valid and consistently formatted, and it ends with general-purpose formatters and a shell script formatter that sit closer to source code.

At a glance: the shortlist in order of fit for this use case
#ToolBest forKey featurePlatforms / deploymentPricingMore
1yamllintyamllintLinting YAML in repos and CIChecks key repetition, line length, trailing spaces and indentationPackaged for all major operating systems; installable with pipSee vendor pricing pageIntroduction
2TaplotamasfeValidating and formatting TOML, including against JSON schemasSupports TOML 1.0.0Cross-platform; available wherever Rust compilesSee vendor pricing pageOfficial site
3dprintdprintTeams that want one formatter for every file type in a repoOfficial plugins for TypeScript/JavaScript, JSON, Markdown, TOML, Dockerfile, SQL and Jupyter notebooksSingle static binary; install via shell script, PowerShell, npm, Homebrew or CargoSee vendor pricing pageIntroduction
4PrettierPrettierTeams that want an automatic style guide with editor and pre-commit useFormats on save in editorsNot stated on official pagesSee vendor pricing pageIntroduction
5BiomeBiomeWeb teams that want formatter and linter in one toolSingle check command runs all tools togetherInstallable via several package managers and integrated into editorsSee vendor pricing pageIntroduction
6shfmtmvdanKeeping shell scripts consistently formatted across a teamDocumented default stylePackages for many operating systems and package managersSee vendor pricing pageIntroduction

1 yamllint

By yamllint

yamllint is a linter for YAML files. It checks syntax validity as well as quirks and cosmetic problems.

Why it is here: It sits first because it is built for one config format, YAML, and checks both validity and style.

Best for
Linting YAML in repos and CI
Key features
  • Checks key repetition, line length, trailing spaces and indentation
  • Lints single files or recursively lints a directory
  • Pre-defined configs such as 'relaxed', plus custom config files
  • Special comments disable checks for a line or a block
  • Parsable output format for editor syntax checking
Limits
Documented for YAML only; teams that also keep TOML or other formats in the repo will need another tool for those files.
Platforms / deployment
Packaged for all major operating systems; installable with pip
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

2 Taplo

By tamasfe

Taplo is a toolkit for TOML that offers validation, formatting and a language server.

Why it is here: It comes second because it targets TOML specifically and pairs validation with a configurable formatter.

Best for
Validating and formatting TOML, including against JSON schemas
Key features
  • Supports TOML 1.0.0
  • Validates syntactically or against JSON schemas
  • Formatter with fine-grained, customizable options
  • Embeddable language server based on JSON schemas
  • Usable in Visual Studio Code, on the command line or as a library
Limits
Documented for TOML only; teams that need YAML or JSON handled should check the vendor documentation or pair it with another tool.
Platforms / deployment
Cross-platform; available wherever Rust compiles
Pricing
See vendor pricing page (not quoted here; facts checked 22 November 2026, Asia/Dhaka)

3 dprint

By dprint

dprint is a pluggable, configurable formatting platform written in Rust. It formats many languages through one CLI.

Why it is here: It is third because one tool and one config file can cover TOML, JSON and Markdown, while also formatting source code.

Best for
Teams that want one formatter for every file type in a repo
Key features
  • Official plugins for TypeScript/JavaScript, JSON, Markdown, TOML, Dockerfile, SQL and Jupyter notebooks
  • dprint init scaffolds a dprint.json configuration file
  • dprint check verifies that code is already formatted
  • Plugins can be pinned and versioned in config
  • Single static binary with no runtime dependencies
Limits
The official plugins listed in the facts do not include YAML; teams that need YAML formatting should check the vendor documentation for community or wrapper plugins.
Platforms / deployment
Single static binary; install via shell script, PowerShell, npm, Homebrew or Cargo
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

4 Prettier

By Prettier

Prettier is an opinionated code formatter that integrates with most editors and enforces a consistent style automatically.

Why it is here: It sits fourth because it is a general-purpose formatter whose documented strengths are editor integration and ending style debates, rather than config formats.

Best for
Teams that want an automatic style guide with editor and pre-commit use
Key features
  • Formats on save in editors
  • Runs as part of pre-commit scripts or githooks
  • Can clean up an existing inconsistent codebase quickly
  • Removes style discussions from code review
  • Aims to use the least controversial coding styles
Limits
The pages summarised here do not list which config formats it supports; confirm YAML and TOML coverage in the vendor documentation.
Platforms / deployment
Not stated on official pages
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

5 Biome

By Biome

Biome is a Rust-based web toolchain that formats and lints code for JavaScript, TypeScript, CSS and other web languages.

Why it is here: It comes fifth because it is aimed at web projects, and YAML support is a recent addition rather than its core focus.

Best for
Web teams that want formatter and linter in one tool
Key features
  • Single check command runs all tools together
  • Formatter highly compatible with Prettier
  • Detailed, contextual diagnostics
  • Some lint diagnostics offer safe automatic fixes
  • Biome v2.6 adds Markdown, SCSS and YAML support
Limits
YAML support is documented as part of v2.6; TOML is not mentioned, so teams with TOML files should check the vendor documentation.
Platforms / deployment
Installable via several package managers and integrated into editors
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

6 shfmt

By mvdan

shfmt is a shell script formatter from the mvdan/sh project, which also provides a shell parser and interpreter for POSIX Shell, Bash, Zsh and mksh.

Why it is here: It is last because it formats shell scripts rather than config files, though those scripts often sit alongside config in the same repos.

Best for
Keeping shell scripts consistently formatted across a team
Key features
  • Documented default style
  • Supports POSIX Shell, Bash, Zsh and mksh
  • Converts shell to and from a JSON syntax tree
  • sh-checker GitHub Action performs static analysis using shfmt
  • Release tags published as Docker images
Limits
Documented for shell scripts only. The project deliberately limits formatting options, and formatting cannot be disabled for ranges of lines.
Platforms / deployment
Packages for many operating systems and package managers
Pricing
See vendor pricing page (not quoted here; facts checked 21 November 2026, Asia/Dhaka)

How we chose these tools

We looked at how directly each tool targets config file formats, how well its documented capabilities fit validation and formatting work, and what the vendor documents about installation, platforms and editor or CI use. Tools built for config formats come first. General-purpose code formatters follow, and a formatter for shell scripts comes last because scripts often live beside config in the same repos.

Every fact comes from official vendor pages, with a check date recorded for each source. The order reflects editorial fit for this use case, explained in the "why here" line of each entry. The list is built from documentation rather than product trials, so where a page does not state a capability, we say so and point you to the vendor documentation.

Order used in this guide: Ordered by how directly each tool targets config file formats rather than general source code.

Frequently asked questions

What is a good linter for YAML files?

yamllint is a linter built for YAML. It checks syntax validity, key repetition and cosmetic issues such as line length, trailing spaces and indentation, and it supports custom configuration files.

How do I validate TOML against a schema?

Taplo validates TOML documents syntactically or against JSON schemas. It supports TOML 1.0.0 and can be used in Visual Studio Code, on the command line or as a library.

Can one tool format several config file types?

dprint aims to be a single formatter for every language in a repository, with official plugins for JSON, Markdown, TOML, Dockerfile and others. Biome v2.6 adds Markdown, SCSS and YAML support.

How can I check formatting in CI without changing files?

dprint check verifies that code is already formatted. yamllint can lint a directory recursively and offers a parsable output format, and Prettier can run in pre-commit scripts or githooks.

Is there a formatter for shell scripts?

shfmt formats shell programs with a documented default style and supports POSIX Shell, Bash, Zsh and mksh. A GitHub Action, sh-checker, uses shfmt for static analysis of shell scripts.

Sources. Facts on this page come from each vendor's official pages, checked on the dates shown (Asia/Dhaka):

Linthelm is independent and not affiliated with the vendors listed. No vendor paid for inclusion or position. Product names belong to their owners. Features and prices change; confirm details on each official website.