VSCodium and Open VSX Registry: Extension Compatibility for Proprietary API Checks

Extension Interoperability and Product Identification

VSCodium distributes a telemetry-free version of the VS Code source, utilizing the Open VSX Registry as the primary extension gallery. This is achieved by modifying the product.json configuration to redirect gallery endpoints away from the Microsoft Marketplace.

A technical challenge arises when extensions implement internal checks for the vscode product name or specific proprietary identifiers to enforce licensing or feature availability. Since VSCodium identifies as a distinct distribution, these extensions may fail to activate or restrict functionality despite the underlying API compatibility.

Given the reliance on the Open VSX Registry for distribution, there is uncertainty regarding the standard for handling extensions that explicitly target the official Microsoft binary.

• Does the VSCodium build process provide a mechanism to spoof the product identity for compatibility with such extensions?
• What is the recommended approach for ensuring extension stability when the underlying VS Code version jumps significantly?