The JSON Schema specification
AI Analysis
JSON Schema is a vocabulary and specification for validating, annotating, and manipulating JSON documents. This repository contains the work-in-progress sources for the next IETF Internet Draft specifications. It serves the technical standards community, implementers building JSON Schema validators, and API designers needing structured validation—not general end users.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
JSON Schema specification: the IETF draft defining how to validate and annotate JSON documents
json-schema-spec is the canonical source for the JSON Schema specification, an IETF Internet Draft that defines a vocabulary for validating, annotating, and describing JSON documents. It is used by API designers, tool authors, and platform teams as the normative reference that drives validators (AJV, jsonschema, etc.), form generators, code generators, and API description formats like OpenAPI. This repository is not a library but a living specification document. Its importance is infrastructural: essentially every JSON validation tool in the ecosystem derives its behavior from this spec.
Originated in 2009 as an informal IETF draft. Rehosted on GitHub in 2015. Has gone through draft-04, draft-06, draft-07, and the current 2019-09/2020-12 stable releases, with the next draft actively in progress in this repository.
Growth is slow and steady (7 stars/week) because this is a specification repo, not a library. Its influence is measured in the number of conforming implementations worldwide rather than direct GitHub engagement. The explosion of OpenAPI adoption and JSON-based APIs since 2017 has significantly elevated JSON Schema's importance without dramatically spiking this repo's star count.
Indirect adoption is massive and well-documented: AJV (14k+ stars) implements this spec; OpenAPI 3.x embeds JSON Schema; major cloud providers (AWS, Google, Azure) reference JSON Schema in their API and config validation tooling. Direct production usage of this repo itself is as a normative reference, not a runtime dependency. Adoption of the specification — not this repo — is pervasive.
Appears to be a documentation/specification repository. Sources are Markdown files compiled to HTML using a Remark-based toolchain with custom plugins for section numbering, cross-references, ToC generation, and syntax highlighting. Likely does not contain runtime application logic beyond the build pipeline.
not documented in README — as a specification repository, formal test suites are maintained separately in the JSON-Schema-Test-Suite repository rather than here.
Last push was 2026-06-03, approximately 22 days before the evaluation date, indicating active and recent maintenance. The README references an active contributor label system with prioritized issues, suggesting organized governance. The project badge explicitly states 'Active – The project has reached a stable, usable state and is being actively developed.'
ADOPT IF: you are building a validator, code generator, API description tool, or any system that needs a standardized, IETF-tracked vocabulary for describing and validating JSON data — the spec is the authoritative reference. AVOID IF: you need a ready-to-use runtime library; this repository is a specification source and build pipeline, not executable code. MONITOR IF: you depend on a specific draft version and need to track breaking changes as the next draft progresses toward finalization.
Independent dimensions
Mainstream potential
4/10
Technical importance
9/10
Adoption evidence
8/10
- The specification has historically taken many years between stable draft releases, creating ecosystem fragmentation where different tools implement different draft versions (draft-07 vs 2019-09 vs 2020-12) simultaneously.
- Governance is community-driven and volunteer-dependent; progress on contested issues can stall for extended periods without a formal standards body timeline.
- OpenAPI 3.1 adopted JSON Schema 2020-12 but OpenAPI 3.0 uses a subset of draft-07, meaning the spec's 'canonical' version remains ambiguous in practice for a large portion of the ecosystem.
- The IETF Internet Draft process does not guarantee eventual RFC publication; the spec could remain in perpetual draft status, which may limit formal adoption in regulated or compliance-driven environments.
- Complexity of advanced features (unevaluatedProperties, dynamic references, vocabulary system) means implementer compliance varies, reducing interoperability guarantees even among 'conforming' validators.
The specification will continue its slow, steady progression toward the next stable draft. Ecosystem fragmentation across draft versions will gradually reduce as major validators converge on 2020-12, but full convergence may take another 2-3 years.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- http://json-schema.org/
- Language
- JavaScript
- License
- NOASSERTION
- Last updated
- 7d ago
- Created
- 134mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Proposal: Cross-Property & Dynamic Validation via Common Expression Language (CEL)
✨ Proposal: Support `errorMessage`
✨ Proposal: Support `deprecationMessage`
✨ Proposal: Can we have a 2020-12 meta-schema that enables `format-assertion`?
✨ Proposal: Reference W3C string-meta for language and direction metadata on strings
Top contributors
Recent releases
No releases published yet.
Similar repos
schemaorg/schemaorg
Schema.org is the canonical repository for the Schema.org vocabulary—a...
python-jsonschema/jsonschema
jsonschema is a mature Python implementation of the JSON Schema specification,...
jsonrainbow/json-schema
A PHP library implementing JSON Schema validation with support for Draft-3,...
voxpupuli/json-schema
A Ruby library for validating JSON objects against JSON Schema specifications...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
5.1k | +11 | JavaScript | 8/10 | 7d ago |
|
|
6.1k | — | HTML | 9/10 | 3w ago |
|
|
5k | — | Python | 9/10 | 4d ago |
|
|
3.6k | — | PHP | 7/10 | 1w ago |
|
|
1.6k | — | Ruby | 8/10 | 5d ago |
|
|
1.2k | — | Go | 8/10 | 2w ago |
Schema.org defines semantic vocabularies for structured data on the web; JSON Schema focuses on structural validation and annotation of JSON documents. They address different layers: Schema.org is about meaning, JSON Schema is about shape and constraints. They are not direct competitors.
TypeSpec is a higher-level API description language that can emit JSON Schema among other outputs. It sits above JSON Schema in the abstraction stack and depends on it as a target format, rather than competing with it.
AJV is a JSON Schema validator implementation (not the spec itself). It is a downstream consumer of this specification and one of the most prominent signals of the spec's adoption.
A form rendering library driven by JSON Schema. Again a downstream consumer, not a competitor — its popularity demonstrates the ecosystem value of the specification.
A PHP library for Schema.org structured data, entirely different domain (semantic metadata vs. JSON document validation). Not a meaningful competitor.