google/zx

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.