Discofork
Repository brief

microsoft/vscode

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-29T22:05:27.951Z
3mo ago

microsoft/vscode

microsoft/vscode is the main open-source Code - OSS repository behind Visual Studio Code. It is a very active, widely forked and starred MIT-licensed project with a large codebase, frequent commits, and clear contribution workflows. Forks are most interesting if you want to build on a mature editor platform, experiment with extensions or product variants, or follow upstream VS Code development closely.

GitHub
Loading tags...
Stars183,167
Forks38,824
Default branchmain
Last pushed2026-03-29T21:47:38Z
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

6 of 6 fork briefs
Selected

Choose this fork if your goal is a remote, browser-based VS Code distribution and you value product customization over staying close to upstream. Avoid it if you need near-term upstream parity, stock VS Code workflows, or the strongest extension trust model.

Choose this fork if you want a customized, AI-centric IDE and can accept significant divergence from upstream VS Code. Avoid it if you need close upstream parity, frequent security and bugfix updates, or the lowest-risk maintenance path.

Choose this fork if you want an opinionated AI-first editor and are comfortable owning a heavily diverged VS Code base. Avoid it if you need close upstream parity, fast security/bugfix intake, or minimal maintenance burden.

Choose this fork only if you need its specific legacy customizations or test/perf work. For general editor use, extension development, or a maintainable product base, upstream VS Code is the better default because this fork is stale and materially diverged.

Choose this fork if you want a branded, cross-platform IDE distribution centered on Chinese ecosystem workflows and can accept major upstream lag. Avoid it if you need current VS Code features, low maintenance overhead, or easy upstream compatibility.

Choose this fork if legacy Windows support matters more than staying current with upstream VS Code. Avoid it if you want the latest features, fastest security updates, or low-maintenance upstream compatibility.