VSCodium/vscodium

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.