One command to validate any JSON file against any JSON Schema.

Zero config when your files have $schema. Pipes, globs, remote schemas, and structured JSON output all work out of the box.

npx jsonck data.json
# ✓ valid

• Zero config — reads $schema from your JSON files automatically
• Pipes & globs — curl ... | jsonck --schema url or jsonck *.json
• JSON output — --json gives structured results for scripts, CI, and LLM tool calls
• Fast — single Ajv instance with schema caching, no startup overhead
• Tiny — 5 modules, 4 runtime dependencies, nothing bloated

# No install needed
npx jsonck config.json

# Or install globally
npm install -g jsonck

Requires Node.js >= 20.

jsonck data.json

If the JSON file contains "$schema": "https://...", jsonck downloads and validates against it automatically.

# Local file
jsonck data.json --schema ./schemas/my-schema.json

# Remote URL
jsonck data.json --schema https://example.com/schema.json

The --schema flag always overrides any $schema in the file.

cat data.json | jsonck --schema ./schema.json
curl -s https://api.example.com/data | jsonck --schema ./schema.json
jq '.config' big.json | jsonck - --schema ./config-schema.json

jsonck *.json --schema ./schema.json

Perfect for CI pipelines, scripts, and LLM tool integrations:

jsonck data.json --schema ./schema.json --json

{
  "file": "data.json",
  "valid": false,
  "errors": [
    { "path": "/name", "message": "must be string" },
    { "path": "/age", "message": "must be >= 0" }
  ]
}

Multiple files produce a JSON array.

if jsonck data.json --schema ./schema.json; then
  echo "Deploying..."
else
  echo "Fix your config first."
  exit 1
fi

jsonck [files...] [options]

Text (default) — human-readable. Prints Valid/Invalid to stdout/stderr. Batch mode prefixes each line with the filename.

JSON (--json) — machine-readable. Single file → JSON object. Multiple files → JSON array. Errors are inline, not on stderr. Recommended for scripts, CI, and LLM tool calls.

1. --schema flag (always wins)
2. $schema property in the JSON file
3. Error if neither is found

Schemas are cached per invocation — validating 100 files against the same remote schema downloads it once.

jsonck is designed to work as a tool in LLM agent workflows. Use --json for structured output that's easy to parse:

jsonck config.json --schema https://example.com/schema.json --json

Returns a JSON object with file, valid, and errors fields. Exit code 0 means valid, 1 means invalid, 2 means something broke. No interactive prompts, no color codes in JSON mode — clean machine-readable output.

npm run build        # tsc → dist/
npm test             # vitest (build first — CLI tests exec dist/cli.js)
DEBUG=jsonck jsonck data.json  # debug logging

MIT