Add or Modify schema-parity in JSON Schema Ecosystem

Tool Name

schema-parity

Tool Description

Checks whether a JSON Schema accepts exactly the same set of values as the runtime validator it was generated from (Zod, ArkType, Valibot, TypeBox, or any other schema-to-JSON-Schema generator), and reports every value where the two disagree. Not a linter against the JSON Schema spec, but a differential check between a schema and the tool that produced it.

Example gap it finds: zod 4.4.3's z.toJSONSchema() emits a tuple as prefixItems with no minItems and no items: false, so the generated JSON Schema accepts [], ["a"] and 3+-element arrays that zod's own safeParse rejects on the same tuple type. ArkType, Valibot and TypeBox all emit the length-constrained form on the same input; zod does not. Reported upstream: colinhacks/zod#6455.

Action Type

• Add Tool

Tooling Types

• validator
• util-testing

Languages

TypeScript / JavaScript

Environments

Node.js 18+, browsers, workers. Zero runtime dependencies, dual ESM/CJS

Dependencies on Validators

Runs the schema through whichever JSON Schema validator you already use (examples in the README use ajv); does not bundle or require one itself.

License

MIT

Source Repository URL

https://github.com/tamerkalla/schema-parity

Homepage URL

https://www.npmjs.com/package/schema-parity

Supported Dialects

• 2020-12

Tooling Listing Notes

Library, not a CLI: install it and point it at your own schema/validator pairs. Published with npm provenance attestation.

No target file or test is named. Start by locating how the JSON Schema website records existing ecosystem tools, then add schema-parity using the supplied repository, package, dialect, environment, licensing, and validator details; done means the listing is published with the submitted information and links.