grafana/k6

Choose upstream unless you specifically need this old fork for legacy compatibility or historical reasons. For new adoption, the fork is too stale and too far behind to be a good default.

Prefer upstream unless you specifically need the fork's browser- and upload-related patches; this fork looks like a stale, specialized derivative with significant divergence and a likely ongoing merge burden.

Prefer upstream unless you specifically need this pinned snapshot; the fork adds no visible value and is already behind current k6.

Prefer upstream unless you specifically want an older frozen baseline. This fork has no visible enhancements and is materially behind current k6, so it is mainly useful as a starting point for custom modifications or archival use.

Choose this fork only if its browser/runtime changes are already required and you are prepared to own the maintenance burden. If you mainly want current k6 features, fixes, and dependency hygiene, upstream is the safer default.

Prefer upstream k6 unless you specifically need the fork’s provisioning and browser/build-service changes and are prepared to maintain a large divergence.

Prefer upstream unless you explicitly need this fork's custom behavior and are prepared to maintain a heavily divergent, stale codebase yourself.

Choose upstream unless you specifically need this fork's experimental import.meta.resolve, browser, or runtime changes and are prepared to maintain a large divergence. This fork is better for tinkerers and fork maintainers than for teams wanting a current, low-risk k6 distribution.

Choose this fork only if you need the older behavior it preserves. For new work, upstream k6 is the better default because this fork is materially stale and likely missing newer fixes, protocol/browser improvements, and operational workflows.