Check keywords and declared types
Find a missing type, an unknown type specifier, a keyword that is not recognized for the selected draft, or a keyword used more than once in one schema branch.
Analyze JSON Schemas
JSON Schema Analyzer - A built-in assistant, that runs in the background.
Review structural and quality findings while a JSON Schema is being edited, then return directly to the definition or reference that needs attention.
- Background analysisFindings arrive while editing
- ReferencesDetect unresolved targets
- ConstraintsCompare related keyword values
A companion to schema validation
Surface suspicious schema structures while the document is still in context
The JSON Schema analyzer runs beside the Windows schema editor and reports findings as errors, warnings, or informational messages. It complements formal schema validation by looking for unresolved references, inconsistent constraints, unused definitions, and patterns that deserve an author’s review.
A reported message is evidence to inspect, not an automatic instruction to rewrite the schema. Some constructs are draft-specific or intentional, so the author still decides whether the finding represents a defect.
Inspect local and external references
Report a local $ref whose JSON Pointer cannot be resolved, an external reference whose schema cannot be loaded, or a recursive reference that needs deliberate review.
Compare related constraints
Flag cases such as maximum below minimum, maxLength below minLength, or array-related keywords used without an array type.
Findings retained from the established analyzer
Review structure, references, required properties, and unused definitions
- Required-property consistency: identify a required name that is not defined in the current schema branch.
- Empty constraints: review an empty
not, an empty pattern, or the draft-specific handling of an empty required array. - Repeated definitions: detect a field or property defined more than once at the same branch.
- Unused definitions: find a local definition that is not referenced by the current schema.
- Draft context: interpret unknown keywords and other messages against the schema draft and vocabulary in use.
Severity carries context
The production source explicitly distinguishes messages, warnings, and errors. Confirm the current list of checks, severity mapping, wording, draft behavior, external-resource loading, and any configuration controls before publication.
Platform availability
Choose where to run this workflow
Only platforms supported by approved evidence for this specific workflow are shown. Links are limited to implemented, verified destinations.
- Desktop / WindowsFeatured access: background analysis integrated with JSON Schema editing in JSONBuddy for Windows.
Use the finding
Move from analyzer output to a deliberate schema change
- Select the analyzer result and locate the related schema branch.
- Check the active JSON Schema draft, vocabulary, and reference-resolution context.
- Decide whether the construct is invalid, suspicious, draft-specific, or intentional.
- Correct the schema when appropriate, then validate the schema and rerun representative instance tests.
Continue the schema workflow