YAML / INI Config Linter
Catch tabs, trailing spaces, and malformed key/value lines in config files.
Private by design. Every tool runs 100% in your browser — your code, text, and tokens never leave your device. Nothing is uploaded or stored.
Heuristic checks for tabs, trailing spaces, and malformed key/value lines. It is not a full parser — validate critical configs with the official schema/parser too.
Frequently Asked Questions
Why do tabs break my YAML?
YAML forbids mixing tabs and spaces for indentation; it only accepts spaces. A single tab throws a parse error that is easy to miss in an editor that renders both as whitespace.
What is a trailing-space trap?
Trailing spaces after a key or value can change meaning or cause subtle parse issues. The linter flags them so configs deploy cleanly.
Does this catch all config errors?
It catches the formatting-class errors (tabs, trailing spaces, malformed key/value) that break parsing. Logic errors — wrong values — still need a real validator for your format.