Discofork
Repository brief

VSCodium/vscodium

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:36:04.596Z
1mo ago

VSCodium/vscodium

VSCodium/vscodium is a large, active repository for building freely licensed binary releases of VS Code without Microsoft branding, telemetry, or licensing. It is not presented as a source fork of the editor itself, but as automation and packaging around Microsoft’s `vscode` repo. The project is actively maintained, with recent commits in March 2026, 30,710 stars, and 1,620 forks.

GitHub
Loading tags...
Stars30,710
Forks1,620
Default branchmaster
Last pushed2026-03-27T17:25:06Z
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

8 of 8 fork briefs
Selected

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

Choose this fork if you want a maintained, branded Codex distribution with custom release and installer operations. Choose upstream VSCodium if you want the broader, more generic packaging baseline and the least divergence from VSCodium release automation.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

This fork is materially different enough that adopters should validate long-term maintenance and upgrade cost.

Prefer this fork only if you need its specific build/branding/patch workflow and are willing to own a large rebase burden. For most adopters, upstream VSCodium is the safer choice because this fork is materially stale and likely missing many current fixes and release updates.

Choose this fork only if you specifically need its older custom packaging and branding work. For anyone who wants a current, actively maintained VSCodium base, upstream is the better default.