Why Precise JSON Linting Matters
A single missing comma or trailing brace can break an API, crash an app, or corrupt a config file. Most validators just say "invalid" — this tool tells you exactly which character failed and why.
Trailing Commas
JSON (unlike JS) forbids trailing commas: {"a":1,} is invalid. This linter flags them with the exact position and shows the comma to remove.
Unclosed Braces & Brackets
Every { needs a } and every [ needs a ]. The linter tracks nesting depth and tells you what's missing at which line.
Duplicate Keys
Duplicate object keys are technically parsed by browsers but silently overwrite values. The linter warns you so data isn't lost invisibly.
Wrong Quote Style
JSON requires double quotes. Single-quoted strings like {'key':'val'} are valid JavaScript but invalid JSON. Caught and flagged instantly.
Comments in JSON
// comments and /* block comments */ are not valid JSON. If you need comments, use JSONC or strip them before parsing.
Deep Nesting
Objects nested beyond 10 levels are a linting warning — not an error — but signal a schema design worth reviewing for maintainability.