Discofork
Repository brief

vlang/v

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:44:33.181Z
1mo ago

vlang/v

vlang/v is the upstream repository for the V programming language: a compiled, general-purpose language focused on simplicity, fast compilation, safety, and maintainability. It is very active, with 37k+ stars, 2.2k+ forks, and commits landing as recently as 2026-03-30. Forks are most likely to be interesting if you care about compiler/language work, tooling, formatting, code generation, or standard-library-level changes.

GitHub
Loading tags...
Stars37,449
Forks2,238
Default branchmaster
Last pushed2026-03-30T14:59:26Z
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 only if you need its custom auth/debug additions or a historical V snapshot. If you want current V, upstream is the better base by a wide margin.

Prefer upstream unless you need this fork’s older experimental compiler/toolchain state. The fork is materially stale and highly divergent, so it offers niche value but a high maintenance burden.

Prefer upstream unless you specifically need this fork’s compiler-experiment snapshot or its `-print-v-files`/parse-time tracing behavior. For most adopters, the fork is too stale and too divergent to be a safer or easier base than `vlang/v`.

Prefer this fork only if you specifically need its older experimental V changes or a frozen snapshot. For general V development, upstream is the better choice because this fork is very stale and appears materially harder to maintain or adopt.

Prefer this fork only if you need its local compiler/runtime experiments or customized bundled dependencies. For general adoption, upstream is the safer choice because this fork is significantly behind and highly diverged.

Choose this fork if your goal is V documentation tooling or experimentation on a divergent V codebase. Choose upstream if you want the latest, more stable V compiler and standard toolchain.

Prefer this fork only if you need its specific local patches or a frozen customized V stack. For most adopters, upstream is the safer choice because this fork is materially stale and significantly diverged.

Prefer this fork only if you explicitly need its 2024-local changes. For most adopters, upstream is the better choice because this fork is stale, heavily diverged, and likely missing many newer fixes and compiler features.

Prefer this fork only if you specifically need its historical snapshot or local experiments. For normal V development, upstream is the better choice because this fork is materially stale and heavily diverged.

Prefer this fork only if you need its older 2023 snapshot or specific wasm/eval changes. For most adopters, upstream is the better choice because this fork is very stale and substantially behind current V.