/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

colinhacks/zod

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-31T10:10:35.863Z

1mo ago

colinhacks/zod

Zod is an active, widely used TypeScript-first schema validation library with static type inference. The repository is not archived, is heavily forked and starred, and saw recent commits in February 2026, so forks are currently relevant if you care about staying close to an actively maintained upstream.

Loading tags...

Stars42,254

Forks1,877

Default branchmain

Last pushed2026-02-15T14:20:41Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

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.

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.

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.

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.

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.

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.

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.

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.

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.

Fork comparison

iKowalchuk/zod

38/100

stale

significant_divergence

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.

Likely purpose

To maintain a custom Zod variant with extra runtime/workflow support, likely including Deno-oriented usage and local documentation/tooling changes, rather than staying closely aligned with upstream release cadence.

Best for

Teams that explicitly need Deno support or fork-local runtime adaptations.; Maintainers who want to control Zod internals and repo tooling rather than track upstream closely.; Users comfortable absorbing merge effort in exchange for custom behavior.

Additional features

Deno-related library, helper, test, and benchmark code under `deno/lib/`, suggesting explicit support for Deno workflows.
Expanded repo-level tooling and dependency layout, including both `pnpm-lock.yaml` and `yarn.lock`, which may make the fork easier to consume in mixed-package-manager environments.
Substantial README and docs rewrites, which may reflect fork-specific usage guidance or packaging instructions.
Expands API, schema, or SDK surface area for downstream integrations and generated clients.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.

Missing features

It lags well behind upstream activity, so adopters miss later February 2026 fixes such as `httpUrl()` strict validation, `abort: true` handling in `.refine()`, and the float exponent fix.
It likely misses newer upstream documentation and maintenance cleanup, including README link fixes, tree-shaking metadata, and the removal of deprecated `downlevelIteration` support.
The large deletion count and wide file churn suggest some upstream surfaces are harder to rely on as-is, especially around core schema internals and docs consistency.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you need a fork that already carries custom Deno-oriented work.
Could fit teams that want to own their dependency stack and repo tooling more directly.
Broad divergence implies the fork is not just experimental noise; it likely encodes a deliberate local direction.

Risks

High maintenance burden because upstream is active and the fork is substantially behind and divergent.
Behavioral drift is likely in core validation and type-inference code.
Adopting this fork means giving up a clean path to upstream fixes and docs updates.