iKowalchuk/zod
stale
significant_divergence
Selected Choose this fork only if its Deno-oriented or other local changes are strategically important. For most adopters, upstream Zod is the safer default because it is active and this fork is materially stale and divergent.
kentcdodds/zod
stale
significant_divergence
Prefer this fork only if you specifically need its fork-local changes, especially Deno-oriented work. If you want current Zod behavior, bug fixes, and low-maintenance adoption, upstream is the safer choice.
KATT/zod
stale
significant_divergence
Choose this fork only if you specifically need its divergent runtime/workflow support. If you mainly want Zod as maintained upstream with the lowest compatibility risk, upstream is the safer choice.
AsharibAli/zod
stale
significant_divergence
Prefer this fork only if its Deno/platform changes or other customizations are essential. For most adopters, upstream Zod is the safer choice because this fork is materially divergent and appears stale relative to active upstream development.
Subash-Chand-Thakuri/zod
stale
significant_divergence
Choose this fork only if you specifically need its diverged runtime/workflow direction, especially Deno-related support. For most adopters, upstream Zod is the safer choice because this fork is both stale and heavily rewritten.
JonnyBurger/zod
stale
significant_divergence
Prefer this fork only if you specifically need its Deno/doc-localization customizations and accept significant drift from active upstream. If you want current Zod behavior and lower maintenance risk, upstream is the better default.
GavinMeierSonos/zod
stale
significant_divergence
Choose this fork only if you specifically need its Deno/custom packaging direction or existing team dependency. If you want current Zod behavior with low maintenance risk, upstream is the safer default.
amirhoseinsalimi/zod
stale
significant_divergence
Prefer this fork only if you specifically need its older codebase plus the extra Deno/docs/JSON Schema work and are prepared to own maintenance. For most adopters, upstream Zod is the better default because this fork is materially stale and far behind current fixes and evolution.
renatorib/zod
stale
significant_divergence
Prefer this fork only if you explicitly need the legacy 2021-era Zod codebase, especially for Deno or old API compatibility. For most users, upstream is the better choice because it is actively maintained and much more current.
Choose this fork only if you specifically need a near-upstream snapshot. For most adopters, upstream Zod is the better default because this fork adds no visible features and is already behind by two commits.