Features

🔎 Naming Convention Checks

camelCase, snake_case, PascalCase
Per-key path reporting
Rename suggestions included
Recursive through nested objects

⚡ Quality Scoring

0–100 quality score
Error / warning / info severity
Actionable fix suggestions
JSONPath for each issue

🎯 Structural Checks

Mixed array type detection
Max nesting depth enforcement
Null value flagging
Empty string detection

JSON Linting Guide

What is JSON Linting?

JSON linting goes beyond syntax validation. Valid JSON can still be inconsistent, hard to maintain, or quietly wrong — a schema mixing camelCase and snake_case keys, an array that holds both objects and strings, or a null slipped into a field that's supposed to always have a value. A linter catches these style and structural issues before they turn into confusing bugs downstream, the same way ESLint catches problems that a JavaScript syntax check alone would miss.

This tool runs your JSON through naming-convention checks (detecting the dominant case style and flagging outliers with their exact path), structural checks (mixed-type arrays, excessive nesting depth), and configurable data-quality checks (null values, empty strings), then rolls the results into a single 0–100 quality score with per-issue severity and JSONPath locations.

Common Use Cases

API Design: Ensure consistent field naming across every endpoint before publishing an API contract, since inconsistent casing forces every consumer to special-case fields.
Config Files: Catch stray null fields or empty strings in environment/config JSON before they cause a silent failure at deploy time.
Data Pipelines: Validate that every record in an ingested batch has a consistent shape (no mixed-type arrays) before it hits a strict downstream schema.
Code Review: Run an automated style check on JSON payloads in a PR instead of manually eyeballing naming conventions across dozens of fields.
Onboarding a legacy API: Get a quick quality score and a prioritized list of issues when inheriting a JSON schema you didn't design.

FAQ

Q: Is a score of 100 always achievable?

A: Scores depend on selected checks. Some JSON structures have intentional nulls or mixed arrays — configure checks to match your project's conventions rather than chasing a perfect score on data that's correct as-is.

Q: How is linting different from validation?

A: The JSON Validator checks that your JSON is syntactically well-formed — parseable, no missing commas or brackets. This linter assumes valid JSON and instead checks style and structural conventions on top of that, the same relationship ESLint has to a JavaScript parser.

Q: What counts as a "mixed array"?

A: An array where elements have different JSON types — for example [1, "two", {"three": 3}] mixes a number, a string, and an object. Mixed arrays are usually a sign of an inconsistent API response or accidental data corruption, since most consumers expect every element to share one shape.

Q: Can I fix issues automatically?

A: The linter reports actionable rename suggestions and exact paths for every issue, but doesn't rewrite your JSON automatically — that keeps you in control of naming decisions rather than having a tool silently change field names your application code depends on.

JSON Linter & Style Checker