VSCodium
VSCodium is a community-driven distribution of Microsoft's VS Code editor, built from the same MIT-licensed source code but without Microsoft's proprietary branding and licensing, with Microsoft telemetry disabled by default. The project uses automated build scripts to clone Microsoft's VS Code repository, strip telemetry endpoints and tracking configuration, and produce freely-licensed binaries. Extensions and online-service settings can still send data, as the project privacy documentation warns. VSCodium uses the Open VSX Registry for extensions instead of Microsoft's proprietary Marketplace. The project is maintained by volunteer contributors, funded through community donations, and distributed under the MIT license. It provides the same core editing experience as VS Code while respecting user privacy.
Score generated by AI agents based on publicly cited evidence and reviewed by the project maintainer. Not independently validated. Last assessed 2026-10-30. Score revised 2026-10-30: 4 → 3.
Score History
Timeline events are AI-curated from public reporting. Score trajectory is derived from documented events.
VSCodium's repository was created in August 2018 to publish MIT-licensed builds of Microsoft's VS Code source with Microsoft branding removed and telemetry disabled. Early builds still used Microsoft's Marketplace for extensions, so users had the same catalogue as VS Code. The project ran on volunteer labor and GitHub infrastructure with no revenue model; its only structural risk was a small maintainer base.
Pull request #404, merged on May 20, 2020, switched VSCodium's default extension gallery from Microsoft's Marketplace to the Open VSX Registry, which then held only 218 extensions. That settled the Marketplace terms problem but opened a lasting extension gap, widened by Pylance rejecting non-Microsoft builds from October 2020 and Microsoft retiring its open-source Python language server in 2021. Open VSX nearly shut down in early 2023 before an Eclipse working group funded it, and in November 2024 VSCodium removed Microsoft Marketplace URL examples from its documentation.
Microsoft's C/C++ extension 1.24.5, released April 3, 2025, refused to run outside Microsoft's products, extending the checks Pylance already used to another widely used extension. The same months exposed Open VSX's fragility: an April storage outage left users unable to install extensions for about a day, and a May 2025 report of a publishing flaw (CVE-2025-6705) led Eclipse to deactivate 81 extension versions as a precaution. VSCodium itself kept shipping builds; the pressure came from Microsoft's licensing and the registry it depends on.
From October 2025 Open VSX became a repeated target: leaked publisher tokens were revoked on October 21, GlassWorm returned in waves through spring 2026, a malicious Nx Console version was served for about 36 minutes in May 2026, and 77 counterfeit extensions appeared in late July. The Eclipse Foundation responded with token scanning, pre-publication checks, a hybrid AWS and on-premises setup, immutable published versions and trusted publishing. VSCodium's own conduct did not change: it kept tracking upstream, restored ARM32 builds, and in October 2026 stripped the Copilot integration and Modern UI that Microsoft made default in VS Code 1.143.
Alternatives
Modern, high-performance code editor built in Rust with native collaboration features. Its source is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components. Zed markets faster startup and lower resource use than VS Code, including on large codebases; actual performance depends on the workload. Growing extension ecosystem but smaller than VS Code's. Good choice for developers who want speed and a fresh start from the VS Code ecosystem.
The upstream editor VSCodium is built from — same MIT-licensed source code but with Microsoft's branding, telemetry, and proprietary licensing. Access to Microsoft's Extension Marketplace gives it a broad extension ecosystem. Choose VS Code if extension availability matters more than telemetry concerns. Settings and keybindings can be copied between the editors.
Dimensional Breakdown
Summaries below were written by AI agents based on the cited evidence. They are editorial interpretations, not independent research findings.
Dimension History
Timeline (45 events)
Microsoft Open-Sources VS Code Under MIT License
Microsoft released the source code of Visual Studio Code under the MIT license on GitHub. However, the distributed binary remained under Microsoft's proprietary license with telemetry enabled, creating the gap that would later motivate VSCodium's creation.
VSCodium Repository Created on GitHub
The VSCodium project was created on GitHub by developer stripedpajamas with the goal of producing freely-licensed binary releases of VS Code without Microsoft's proprietary branding, telemetry, and licensing. Build scripts automated the process of cloning Microsoft's vscode repo and producing MIT-licensed binaries.
VSCodium Gains Early Hacker News Attention
VSCodium appeared on Hacker News within weeks of its creation, sparking discussion among developers about Microsoft's telemetry practices in VS Code.
Parrot OS 4.4 Includes VSCodium as Default Editor
Parrot Security OS version 4.4 adopted VSCodium as its default advanced code editor, replacing Atom. Parrot OS described VSCodium as lighter and faster than both Atom and VS Code, with a smaller memory footprint.
VSCodium 1.30.1 Release Published
VSCodium version 1.30.1 was published on GitHub, with Linux and macOS binaries uploaded on December 19, 2018 and Windows binaries added on December 22. The release followed VS Code's versioning scheme, continuing the automated build pipeline that kept VSCodium in sync with upstream.
Visual Studio Magazine Profiles VSCodium Privacy Stance
Visual Studio Magazine published 'Worried About Privacy? VSCodium Strips Microsoft Telemetry from VS Code, with FOSS License,' bringing mainstream developer media attention to the project. The article highlighted the distinction between VS Code's MIT-licensed source and its proprietary distributed binary.
VSCodium Community Discusses Renaming the Project to Codium
A community discussion opened about renaming VSCodium to Codium to remove Visual Studio from the project name. On June 12, a maintainer noted that the binary was already called codium; the discussion continued over whether to rename the application and project, which retained the VSCodium name.
Open VSX Registry Launches as Marketplace Alternative
In April 2020, TypeFox launched the Open VSX Registry at open-vsx.org as a vendor-neutral, open-source alternative to Microsoft's Visual Studio Marketplace. The registry provided an API compatible with VS Code's marketplace protocol, enabling non-Microsoft editors to access extensions without violating Microsoft's terms of use.
VSCodium Integrates Open VSX as Default Extension Registry
Pull request #404 merged, switching VSCodium's extension gallery from Microsoft's Marketplace to Open VSX Registry. At the time, Open VSX contained only 218 extensions compared to the Marketplace's thousands. The change resolved the legal ambiguity of VSCodium accessing Microsoft's restricted Marketplace.
VSCodium Users Report Built-in Settings Sync Unavailable
A VSCodium issue opened on Aug 21, 2020 reported that the built-in Settings Sync introduced in VS Code 1.48 was absent from VSCodium's Manage menu. A later comment in the issue said the sync feature was available in Microsoft's Visual Studio Code but not VSCodium.
Eclipse Foundation Assumes Open VSX Registry Management
TypeFox transferred management of the Open VSX Registry to the Eclipse Foundation under the Eclipse Cloud Development Tools Working Group. The move provided institutional backing and governance structure for the registry that VSCodium and other VS Code forks relied on for extensions.
VS Code Releases Native Apple Silicon Builds
Microsoft released VS Code v1.54 with native Apple Silicon (M1) support, enabling users to run VS Code without Rosetta emulation. VSCodium also faced Apple Silicon build-infrastructure challenges, documented in later community issues.
Microsoft Archives Open-Source Python Language Server in Favor of Pylance
Microsoft archived its open-source Python Language Server in favor of the proprietary Pylance extension. Pylance was restricted to Microsoft products and blocked from non-official VS Code builds; VSCodium users could use alternatives such as the open-source Jedi language server.
VS Code Deprecates Telemetry Opt-Out in Favor of New Setting
VS Code version 1.61 deprecated telemetry.enableTelemetry in favor of telemetry.telemetryLevel, which defaulted to on. Previously disabled telemetry remained disabled because VS Code honored the more restrictive setting. The change prompted confusion about whether existing opt-outs still worked.
Microsoft Kills Open-Source Python Language Server Entirely
The November 2021 Python extension release ended support for the open-source Microsoft Python Language Server, automatically migrating remaining users who had not chosen another server to proprietary Pylance. VSCodium users faced Pylance's proprietary license and environment checks and could use alternatives such as Jedi.
Blog Post Exposes VS Code Licensing Dual-License Structure
A blog post titled Visual Studio Code May Not Be As Open Source As You Think detailed how Microsoft builds VS Code from MIT-licensed source but distributes it under a proprietary license with telemetry. The article highlighted VSCodium as the FLOSS alternative.
Eclipse Foundation Threatens to Decommission Open VSX
The Eclipse Foundation announced it would be forced to decommission the Open VSX Registry by the end of May 2023 if sustainable funding could not be secured. The threat highlighted the fragility of the extension infrastructure that VSCodium and other VS Code forks depended on.
Open VSX Working Group Formed, Saving Registry from Closure
The Eclipse Foundation announced the formation of the Open VSX Working Group with founding members Google, Huawei, Posit, Salesforce, Siemens, and STMicroelectronics. The working group provided sustainable governance and funding for the registry, resolving the decommission threat. At the time, Open VSX hosted nearly 3,000 extensions from over 1,500 publishers.
Radworks Offers VSCodium Funding Through Drips
A Radworks core contributor announced a decision to donate funds to VSCodium through Drips, a FOSS funding initiative, and identified VSCodium as one of its most critical dependencies. In February 2024, the contributor was still asking what prevented the maintainers from starting the claim process.
VSCodium macOS Build Rejected by Gatekeeper
VSCodium version 1.85.2 was rejected by macOS Gatekeeper due to an unnotarized Developer ID, preventing users from running the app without manual security overrides. The incident highlighted the challenge volunteer projects face in maintaining Apple's code-signing requirements across release cycles.
VSCodium Removes Microsoft Marketplace Endpoint Examples from Documentation
A VSCodium documentation commit titled “docs: remove infringing urls” removed the Microsoft Marketplace endpoint examples from the instructions for configuring a different extension gallery. The revised text quoted Microsoft’s terms limiting Marketplace Offerings to Visual Studio Products and Services and said VSCodium could not help users who intend to infringe those terms.
VSCodium Downloads Domain SSL Certificate Invalid
The SSL certificate for downloads.vscodium.com was signed by an untrusted certificate authority, causing ERR_CERT_AUTHORITY_INVALID errors for users attempting to download or update VSCodium. The issue did not affect VS Code, highlighting infrastructure reliability gaps in the volunteer-maintained project.
Microsoft Blocks C/C++ Extension from Running in VS Code Forks
Microsoft released C/C++ extension v1.24.5 with an embedded environment check that prevented it from running in non-Microsoft editors including VSCodium and Cursor, displaying an error that it may only be used with Microsoft products. Pylance had already used similar checks; this extended technical enforcement of Microsoft's licensing to another widely used extension.
Open VSX Registry Suffers Prolonged Storage Outage
Open VSX users reported being unable to install extensions during an outage discussed on Hacker News on April 24, 2025 as lasting 24 hours. Eclipse Foundation records show a broader storage incident began on April 23 and was still being recovered on April 24; an April 25 update reported Open VSX restored on legacy storage. The disruption highlighted reliance on centralized extension infrastructure.
Critical Vulnerability Found in Open VSX Publication Process
Koi Security researchers reported CVE-2025-6705's underlying vulnerability in Open VSX's automated publishing system on May 4, 2025. Missing isolation between build processes could expose a privileged token and allow unauthorized extension uploads. Eclipse deployed a fix on June 24. Its subsequent audit found no evidence of compromise among 65 extensions comprising 81 published versions; all 81 versions were deactivated as a precaution.
Microsoft Announces Plan to Open-Source Copilot Chat Extension
Microsoft announced it would open-source the GitHub Copilot Chat extension under the MIT license, marking a step toward making VS Code a more transparent AI editor. The move was driven by demand for transparency in AI-assisted developer tools and could benefit VSCodium if AI features become available in the open-source codebase.
Eclipse Foundation Revokes Leaked Open VSX Tokens
Following a report from Wiz identifying extension publishing tokens inadvertently exposed in public repositories, the Eclipse Foundation revoked all affected tokens. A small number of malicious extensions had been published using the leaked credentials. The incident was declared fully contained on October 21, 2025.
Eclipse Foundation Announces Open VSX Token and Publication Scanning Safeguards
The Eclipse Foundation said it introduced a token prefix format with MSRC to improve detection of exposed Open VSX tokens. It also said it was implementing shorter default token lifetimes and automated scanning of extensions at publication after the October token leak and malware incident.
AWS Invests in Strengthening Open VSX Infrastructure
Amazon Web Services made a strategic investment to strengthen the reliability, performance, and security of the Eclipse Foundation's infrastructure including the Open VSX Registry. The announcement said AWS infrastructure and services would improve availability, performance, and scalability.
GlassWorm Malware Returns to Open VSX in Three Extensions
BleepingComputer reported that GlassWorm had returned to Open VSX in three new extensions, which had already been downloaded over 10,000 times. The report said the malware targeted GitHub, npm and Open VSX account credentials and cryptocurrency wallet data.
Open VSX Search and Query Services Suffer Extended Disruption
The Eclipse Foundation status page listed the Open VSX Search API, Query API and one other service as down on November 19. Its incident timeline ran from 2:53am UTC to 1:46pm UTC and included repeated service updates.
VS Code Forks Found Recommending Missing Extensions as Supply Chain Risk
Researchers discovered that VS Code forks including Cursor, Windsurf, and Google Antigravity inherited recommended extension lists from Microsoft's marketplace, but those extensions did not exist in Open VSX. Bad actors could register the unclaimed namespaces and publish malicious packages. Cursor, Windsurf, and Google rolled out fixes, and the Eclipse Foundation enforced registry-level safeguards.
Eclipse Foundation Plans Pre-Publish Security Checks for Open VSX
The Eclipse Foundation announced plans for pre-publication security checks for Open VSX extensions. Its staged rollout planned monitoring without blocking in February 2026 and a move toward enforcement in March once checks behaved predictably. The framework would quarantine suspicious uploads for review.
GlassWorm Malware Compromises Open VSX Developer Account
Four established Open VSX extensions published by a legitimate developer had malicious versions published after the developer's account was compromised by the GlassWorm malware campaign. The attack used a compromised account rather than creating new packages, making detection more difficult.
Open VSX Pre-Publish Scanning Bypass Disclosed and Patched
Researchers reported that an attacker with a free publisher account could flood the Open VSX publish endpoint with malicious VSIX uploads, exhaust database connections, and prevent scan jobs from being enqueued. The Hacker News reported that the issue was responsibly disclosed on February 8 and fixed in Open VSX 0.32.0 during February.
Open VSX Surpasses 300 Million Monthly Downloads
The Eclipse Foundation announced the Open VSX Registry surpassed 300 million monthly downloads with over 10,000 extensions from 6,500+ publishers. The registry now powers developer platforms including VSCodium, Cursor, Windsurf, Amazon Kiro, and Google Antigravity, establishing it as critical developer infrastructure.
GlassWorm Campaign Expands to 72 Malicious Open VSX Extensions
The Socket Research Team identified at least 72 additional malicious Open VSX extensions since January 31, 2026, targeting developers with credential-stealing malware disguised as linters, formatters, code runners, and AI coding tools. The extensions abused extensionPack and extensionDependencies to pull in separate GlassWorm-linked extensions in later updates. Related GlassWorm activity in GitHub repositories and npm packages used invisible Unicode characters to conceal payloads.
GlassWorm Campaign Adds 73 Sleeper Extensions to Open VSX
Socket reported a new cluster of 73 impersonation extensions on Open VSX associated with the GlassWorm campaign. The extensions did not initially contain malware and were published by newly created GitHub accounts before later being updated through the ordinary extension update path.
Malicious Nx Console 18.95.0 Distributed Through Open VSX
The Nx Console maintainer's advisory says the malicious 18.95.0 extension was available through Open VSX from 12:33 to 13:09 UTC on May 18, about 36 minutes. The affected extension could reach editors that install from Open VSX, including VSCodium.
Open VSX Stored XSS Vulnerability Published as CVE-2026-13323
Bloom Security reported that stored cross-site scripting in Open VSX could let an attacker who tricked a publisher into opening a link steal a persistent publishing token and publish a malicious extension update. The Eclipse Foundation shipped a fix in Open VSX 1.0.2 during the week of June 23, before the CVE was published on July 1.
Manifold Finds 77 Counterfeit Extensions on Open VSX
Manifold reported finding 77 Open VSX extensions between July 26 and August 1, 2026, that beaconed to the same newly registered domain. Each republished the name, namespace, and description of a real VS Code Marketplace extension under an account that did not own the namespace or belong to the original author. Nineteen sent detailed information about the machine, open repository, and CI system to the domain.
Open VSX 1.1.0 Makes Published Extension Versions Immutable
The Eclipse Foundation announced Open VSX 1.1.0 and 1.1.1. It said a published extension version could no longer be modified, describing this as a supply-chain consistency measure.
VSCodium Restores ARM32 Builds and Adds AnyLinux AppImage
VSCodium's 1.135.06055 release added AnyLinux AppImage builds and brought ARM32 builds back. The release listed AppImage packages for x86_64 and aarch64, plus ARM32 Debian, RPM, and tarball assets.
Open VSX Deploys Trusted Publishing and Confirms Pre-Publication Checks
The Eclipse Foundation said trusted publishing was available on Open VSX. The post also said every upload continued to go through pre-publication checks regardless of its authentication method.
VSCodium 1.143 Builds Strip Copilot and Microsoft's Modern UI
VSCodium's 1.143 builds, tracking VS Code 1.143.1, disabled the “Modern UI” that Microsoft made default upstream. Linux Compatible reported that maintainer Baptiste Augrain (daiyam) removed the Copilot API service, kept telemetry disabled and dropped automated PR generation from the agent host; a follow-up 1.143.17232 release fixed settings dropdowns broken by the UI change.
Evidence (40 citations)
D1: User Value Erosion
D2: Business Customer Exploitation
D3: Shareholder Extraction
D4: Lock-in & Switching Costs
D5: Twiddling & Algorithmic Opacity
D6: Dark Patterns
D7: Advertising & Monetization Pressure
D8: Competitive Conduct
D9: Labor & Governance
D10: Regulatory & Legal Posture
Scoring Log (6 entries)
4→3. D10 1→0 (recalibration: the prior point rested on Open VSX registry security incidents, which are the Eclipse Foundation's service, not VSCodium's legal posture; VSCodium complies with Microsoft's terms and has no lobbying, enforcement or litigation). Other nine dimensions confirmed. Eras: 'Community Fork Born' re-dated 2018-08-01→2018-08-13 (repository created); 'Open VSX Pivot' re-dated 2020-06-01→2020-05-20 (PR #404 merged), D4 0→1 recalibrated (extension source and directory diverge from VS Code from this point); 'Extension Ecosystem Squeeze' re-dated 2025-01-01→2025-04-03 (C/C++ extension block), summary corrected (Pylance checks date from 2020); 'Supply Chain Pressures' re-dated 2026-02-19→2025-10-21 (Open VSX token revocation, start of sustained malware campaigns), D10 1→0. All 4 kept. Re-tagged 10 Open VSX timeline events and 3 evidence items from D9/D10 to D1. Since Feb 2026: no change in VSCodium's own conduct; Open VSX saw further malware (GlassWorm sleeper wave Apr 2026, Nx Console compromise May 2026, 77 counterfeit extensions Jul 2026) and fixed CVE-2026-13323, while adding immutable versions (Aug) and trusted publishing (Oct); VSCodium restored ARM32 builds (Sep) and stripped Copilot and Modern UI from its 1.143 builds (Oct 2026).
Checked all 4 restore candidates against the current regraded product: 0 restored, 0 partly restored, 4 CONFIRMED REMOVED, 0 already present. timeline:update:2 — CONFIRMED REMOVED: the August 27, 2018 Hacker News page supports telemetry discussion but no qualifying source established HN-caused Linux/FOSS adoption or the removed participant characterization. timeline:update:3 — CONFIRMED REMOVED: GBHackers (November 28, 2018) supports the Atom replacement and performance comparison already retained, not first inclusion in any Linux distribution or privacy validation. timeline:update:14 — CONFIRMED REMOVED: the full Keyboard Playing article (January 14, 2022; modified July 7, 2023) supports the retained licensing explanation and VSCodium recommendation, not wide sharing or attributable user growth. timeline:update:17 — CONFIRMED REMOVED: GitHub issue #1711 records the November 2023 donation decision and February 2024 claim-process question, not January 2024 receipt or funding scarcity. Radworks November 8, 2023 announcement names other recipients; current official FUNDING.json shows a Drips wallet, not historical receipt or number of funding sources. Read all four cited live pages, attempted all four Wayback copies before searching, and ran three targeted queries per candidate including origin/date-drift checks. Archive failures, a Drips page without readable funding data and two attempted Parrot origin URLs returning 404 were not treated as disproof. No source found established the dropped claims. Detailed queries and source outcomes: work/restore-research.json. No content or scores changed; reviewLog only.
Checked 67 timeline/evidence/milestone items plus 2 alternatives and all prose/identity fields. 28 verified, 30 corrected (11 date-only), 9 re-sourced, 2 duplicate citations removed. Contradicted details: first-stable characterization of 1.30.1 (GitHub stable 1.26.1 release, https://github.com/VSCodium/vscodium/releases/tag/1.26.1); ignored legacy telemetry opt-outs (Microsoft release notes https://code.visualstudio.com/updates/v1_61 and issue134660); 81 extensions rather than 81 versions of65 (detailed Eclipse advisory https://blogs.eclipse.org/post/mika%C3%ABl-barbero/eclipse-open-vsx-registry-security-advisory). Five unsupported claim groups: HN-caused adoption, Parrot first Linux inclusion, blog wide-sharing/user growth, funding receipt/scarcity, universal widest-extension-ecosystem superlative. Twelve distinct prose claim groups repaired. Preserved true miscited/misdated details through five supplemental evidence items. No scores changed. [Amended by regrade 2026-10-30: Kept evidence 'VS Code Forks Recommend Missing Extensions Creating Supply Chain Risk' under D10 though the article names Cursor, Windsurf, Google Antigravity and Trae, not VSCodium: removed from evidence and the timeline event re-tagged as registry context. Timeline 'Microsoft Blocks C/C++ Extension...' still called it the first technical enforcement despite Pylance checks from October 2020 already in the record: description corrected.]