Discofork
Repository brief

xai-org/grok-1

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-30T13:30:29.428Z
3mo ago

xai-org/grok-1

xai-org/grok-1 is a small Python/JAX example repo for loading and running the Grok-1 open-weights model. It is actively maintained enough to have recent metadata updates, but the last pushed commit was on 2024-08-30. The repo is widely forked and starred, and its practical value is mainly as a reference implementation for running the released weights, not as a general-purpose app.

GitHub
Loading tags...
Stars51,515
Forks8,468
Default branchmain
Last pushed2024-08-30T04:17: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

9 of 9 fork briefs
Selected

Prefer upstream unless you specifically need this frozen snapshot. This fork adds nothing, is stale, and lags behind upstream documentation and install fixes.

Choose this fork only if you need a private, near-upstream copy. If you want added capabilities or active maintenance, the provided evidence does not show either.

Choose this fork if you want HF integration and weight-conversion support. Stick with upstream if you need the original JAX reference implementation or want the more established, better-known path.

Prefer this fork only if you specifically want a marginally faster and more forgiving checkpoint loader; otherwise upstream is effectively the same repo with broader provenance and no evidence of removal or major divergence.

Choose this fork if you want the same Grok-1 example code with better in-code explanation. Skip it if you need new functionality, active maintenance, or changes to inference behavior.

Prefer upstream unless you specifically want this exact fork snapshot. It adds no clear value over upstream and is slightly behind it.

Prefer upstream unless you specifically need this exact early snapshot. This fork offers no added capabilities and is materially less maintained, so it is mainly useful as a reference baseline.

Prefer upstream unless you explicitly need this frozen older snapshot. This fork adds nothing new and lags on setup/documentation fixes, so it is a poor default adoption target.

Prefer upstream unless you specifically need this older snapshot; this fork adds nothing and is already behind on maintenance fixes.