VSCodium

Free/Libre Open Source Software Binaries of VSCode

Table of Contents

• Download/Install
  • Install with Brew
  • Install with Chocolatey
  • Install with Scoop
  • Install with Package Manager
  • Install via the AUR
  • Flatpak Option
• Why Does This Exist
• More Info
• Supported OS

Download/Install

🎉 🎉 Download latest release here 🎉 🎉

More info / helpful tips are here.

Install with Brew (Mac)

If you are on a Mac and have Homebrew installed:

brew cask install vscodium

Note: if you see "App can’t be opened because it is from an unidentified developer" when opening VSCodium the first time, you can right-click the application and choose Open. This should only be required the first time opening on a Mac.

Install with Chocolatey (Windows)

If you use Windows and have Chocolatey installed (thanks to @Thilas):

choco install vscodium

Install with Scoop (Windows)

If you use Windows and have Scoop installed:

scoop bucket add extras
scoop install vscodium

Install with Package Manager (Linux)

You can always install using the downloads (deb, rpm, tar) on the releases page, but you can also install using your favorite package manager and get automatic updates. @paulcarroty has set up a repository with instructions here. Any issues installing VSCodium using your package manager should be directed to that repository's issue tracker.

Install via the AUR (Arch Linux)

Install with your favorite AUR helper, such as yay:

yay -Sy vscodium

Flatpak Option (Linux)

VSCodium is not available as a Flatpak app, but @amtlib-dot-dll has done significant work to package up the open source build of Visual Studio Code without telemetry, very similarly to VSCodium. That package is available here and the build repo is here.

Why Does This Exist

This repository contains a build file to generate FLOSS release binaries of Microsoft's VSCode.

Microsoft's downloads of Visual Studio Code are licensed under this not-FLOSS license and contain telemetry/tracking. According to this comment from a Visual Studio Code maintainer:

When we [Microsoft] build Visual Studio Code, we do exactly this. We clone the vscode repository, we lay down a customized product.json that has Microsoft specific functionality (telemetry, gallery, logo, etc.), and then produce a build that we release under our license.

When you clone and build from the vscode repo, none of these endpoints are configured in the default product.json. Therefore, you generate a "clean" build, without the Microsoft customizations, which is by default licensed under the MIT license

This repo exists so that you don't have to download+build from source. The build scripts in this repo clone Microsoft's vscode repo, run the build commands, and upload the resulting binaries to GitHub releases. These binaries are licensed under the MIT license. Telemetry is disabled.

If you want to build from source yourself, head over to Microsoft's vscode repo and follow their instructions. This repo exists to make it easier to get the latest version of MIT-licensed VSCode.

Microsoft's build process does download additional files. This was brought up in Microsoft/vscode#49159 and Microsoft/vscode#45978. These are the packages downloaded during build:

• Extensions from the Microsoft Marketplace:
  • ms-vscode.node-debug2
  • ms-vscode.node-debug
• From Electron releases (using gulp-atom-electron)
  • electron
  • ffmpeg

More Info

For more information on getting all the telemetry disabled and tips for migrating from Visual Studio Code to VSCodium, have a look at this Docs page.

Please note that some Visual Studio Code extensions have licenses that restrict their use to the official Visual Studio Code builds and therefore do not work with VSCodium. See this note on the Docs page for what's been found so far and possible workarounds.

Supported OS

• OSX x64 (zipped app file)
• Linux x64 (.deb, .rpm, and .tar.gz files)
• Linux x86 (.deb, .rpm, and .tar.gz files)
• Windows x86
• Windows x64

The ARM architecture is not currently supported but is being worked on.

License

MIT