/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

google/zx

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-30T12:04:02.519Z

3mo ago

google/zx

`google/zx` is an actively maintained Node.js/TypeScript project for writing better scripts. It has strong adoption (`45,321` stars, `1,233` forks), recent activity as of `2026-03-28`, and ships as both a library and CLI with docs, examples, tests, and build tooling. The repository looks mature and release-oriented rather than experimental.

Loading tags...

Stars45,321

Forks1,233

Default branchmain

Last pushed2026-03-28T15:48:25Z

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 you need the Deno-specific heritage or its older zx API shape. For most users, upstream zx is the safer choice because this fork is stale, heavily behind, and unlikely to have current runtime, packaging, or bugfix coverage.

Prefer this fork only if you specifically need its CommonJS compatibility posture. For most new adopters, upstream `google/zx` is the better default because it is actively maintained and materially ahead on fixes, compatibility, and documentation.

Choose this fork only if you want its core behavioral changes or trimmed distribution and are prepared to absorb the maintenance cost. If you want the broadest compatibility, freshest fixes, and upstream docs/tooling, upstream is the safer default.

Prefer this fork only if its extra `ProcessPromise` and local-execution conveniences exactly match your workflow and you are comfortable freezing on an old upstream base. If you want current zx behavior, fixes, and lower maintenance risk, upstream is the better choice.

Choose this fork only if concurrency-focused behavior is the main requirement and you can accept being materially behind upstream. For most adopters, upstream zx is the safer default because it is active, broader in compatibility, and much better maintained.

Prefer upstream unless you specifically need the fork's standalone/distribution-oriented behavior or must preserve a legacy 2022 snapshot. This fork is materially stale and diverged enough that it will cost more to maintain than to adopt.

Choose upstream unless you specifically need this fork's historical packaging/export behavior. This fork looks materially stale and substantially diverged, so it is better for compatibility with old integrations than for adopting current zx capabilities.

Choose this fork only if you specifically need its older customized behavior, especially markdown-script support. For most users, upstream zx is the better default because it is active, much more current, and likely safer to adopt.

Prefer upstream for almost all new work. Use this fork only if you need a legacy frozen zx version and accept the maintenance burden.

Choose upstream unless you specifically need the fork's older Node 14-oriented behavior or its local CLI/documentation tweaks. For new adopters, the fork is too stale and too far behind to be the safer default.

Fork comparison

Minigugus/zx-deno

38/100

stale

significant_divergence

Choose this fork only if you need the Deno-specific heritage or its older zx API shape. For most users, upstream zx is the safer choice because this fork is stale, heavily behind, and unlikely to have current runtime, packaging, or bugfix coverage.

Likely purpose

To provide a Deno-oriented zx variant with a few early API/CLI tweaks and documentation changes for users who wanted zx-like shell scripting outside upstream’s main runtime focus.

Best for

Developers maintaining an old Deno-based zx integration; Teams that explicitly want a lightweight historical zx fork instead of current upstream; Adopters who value a frozen API and can tolerate maintaining their own fixes

Additional features

Deno-oriented packaging and distribution via `deno.land/x/zx_deno`
Support for using an absolute path with the `zx` CLI binary
Custom promisify behavior for better interoperability
Early convenience additions like `$.prefix` and `$.quote`
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 far behind upstream maintenance and bugfixes, with 210 upstream commits missing and no recent activity since 2021-09-09
It likely misses newer upstream runtime and compatibility improvements for Node.js, Bun, GraalVM Node.js, and the broader current release pipeline
Recent upstream shell-quoting and preset behavior fixes are absent, including newer safety/ergonomics changes such as `.sync` shortcut support
Upstream documentation, tests, build tooling, and packaging refinements appear to be out of date or replaced by an older fork snapshot
It trails upstream by 210 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you specifically want zx-style scripting in a Deno-centered workflow
Small, early ergonomic additions for quoting and CLI invocation
Could be simpler than current upstream for adopters who prefer an older frozen API surface

Risks

Very stale relative to upstream, so behavior and dependencies are likely outdated
Material divergence increases the chance of missing bugfixes and compatibility updates
Adopters may need to patch runtime, docs, or tooling issues themselves
The fork’s long inactivity makes it risky for new production use

google/zx · Discofork