Discofork
Repository brief

jqlang/jq

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-30T20:03:12.244Z
1mo ago

jqlang/jq

jq is a mature, actively maintained command-line JSON processor for slicing, filtering, mapping, and transforming structured data. It has high adoption, an active recent commit history, and a large fork ecosystem, which makes it relevant if you want a widely used C-based utility with many downstream variants.

GitHub
Loading tags...
Stars33,937
Forks1,711
Default branchmaster
Last pushed2026-03-28T06:12:29Z
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
Selected

Choose this fork if WASI/WebAssembly support is the main requirement. Choose upstream jq if you want the most current, actively maintained command-line JSON processor.

Prefer this fork only if you specifically need its binary/Unicode edge-case semantics; otherwise upstream jq is the safer choice because it is far more current, actively maintained, and less risky to adopt.

Prefer upstream jq unless you specifically need this fork's older release/build workflow or legacy platform support. For most adopters, the fork's staleness and divergence are a bigger liability than its added conveniences.

Prefer this fork only if the GUI workflow is the main requirement and you can tolerate being materially behind upstream jq; otherwise, upstream jq is the safer choice for compatibility, fixes, and ongoing maintenance.

Prefer upstream jq unless you specifically need this fork's legacy behavior or local customizations. Choose the fork only if its existing patches are required and you are prepared to maintain a significant downstream delta.

Prefer upstream jq unless you specifically need this old fork's historical behavior or its small set of extra CLI/documentation features. The fork is materially stale and divergent, so it is a poor choice for users who want current fixes, stability, and ongoing maintenance.

Prefer upstream jq unless you specifically need this fork as a private baseline or staging area. It adds no visible value and is already slightly behind upstream.

Choose upstream jq unless you specifically need a personal fork at this exact historical point. This fork is effectively upstream plus lag, not a differentiated downstream.

Choose upstream unless you specifically need an older pinned jq snapshot; this fork adds no visible capabilities and lags important upstream fixes.

Prefer upstream jq unless you specifically need this fork’s repository identity; this fork adds no visible value and is behind current upstream fixes.