/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

grafana/k6

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-30T15:22:27.061Z

1mo ago

grafana/k6

grafana/k6 is an active, widely used load-testing tool written in Go with JavaScript scripting. It has strong community traction (30,242 stars, 1,519 forks) and very recent upstream activity, including changes on 2026-03-27 and 2026-03-30. The repo is a full product codebase, not a small library, with CLI, docs, examples, packaging, cloud integration, extensions, metrics, and vendorized dependencies.

Loading tags...

Stars30,242

Forks1,519

Default branchmaster

Last pushed2026-03-30T15:03:43Z

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

Adopt this only if you explicitly need its legacy fork behavior. For most users, upstream grafana/k6 is the better choice because this fork is stale, far behind, and likely missing many current features and fixes.

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.

Fork comparison

AbdelouahabMbarki/k6

38/100

stale

significant_divergence

Adopt this only if you explicitly need its legacy fork behavior. For most users, upstream grafana/k6 is the better choice because this fork is stale, far behind, and likely missing many current features and fixes.

Likely purpose

To maintain a customized internal variant of k6 with older runtime and CI behavior, rather than to track upstream k6 releases.

Best for

Teams already depending on this exact fork and unwilling to migrate immediately.; Engineers maintaining a private k6 variant for legacy behavior.; Users who need to study or recover older k6 internals rather than run a current load-testing tool.

Additional features

Older fork-specific runtime changes such as global VU IDs and segmented-index executor behavior.
Fork-only CI/process customization, including testing against the latest stable Go from that era.
A legacy codebase that may appeal to users who need the pre-2021 behavior of k6 internals or APIs.
Changes agent workflow behavior, such as prompt handling, handoffs, worktrees, memory, or orchestration flow.
Adds performance-oriented execution paths, caching, or faster runtime modes.

Missing features

It is far behind upstream, so it likely lacks years of browser, metrics, cloud, and extension improvements shipped in grafana/k6 since 2021.
Upstream security, dependency, and compatibility updates are missing, including recent grpc and toolchain bumps.
Recent upstream workflow additions and fixes, such as secret-source handling and browser locator retries, are not present here.
The fork does not appear to track current upstream release management or active maintenance.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 228 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Large preexisting k6 codebase with the core load-testing architecture already present.
May preserve behavior that depended on older k6 internals.
Could be useful as a historical base for specialized patches or private tooling.

Risks

Very high merge cost to rebase onto current upstream.
Staleness makes security, dependency, and compatibility risk high.
The huge diff suggests behavior may be hard to reason about and test confidently.
Users adopting it are likely taking on an effectively unmaintained distribution.