Open VSX default vs. manual Microsoft Marketplace configuration for extension credential consistency in VSCodium

VSCodium ships with the Open VSX Registry as its default extension source to keep the build free of Microsoft telemetry and branding. This default ensures a privacy‑focused environment but means that extensions are available only when their publishers opt in to Open VSX, which can result in version lags compared to the Microsoft Marketplace.

For extensions that handle OAuth credentials (e.g., GitHub Pull Requests, cloud provider plugins), the authentication flow relies on the OS keychain and is unchanged by the gallery source. However, if the Open VSX version lags behind the latest release, any fixes or improvements to token‑expiry handling or refresh logic may be missing, potentially affecting the user experience when credentials expire.

The trade‑off is therefore between retaining the default privacy‑preserving registry and manually pointing VSCodium to the Microsoft Marketplace to obtain the most recent extension versions, accepting the associated licensing and compliance considerations. Users must decide which approach better serves their need for consistent credential‑handling behavior.

Does manually configuring the Microsoft Marketplace in VSCodium provide noticeable improvements in OAuth token expiry handling compared to the default Open VSX source?

Is there a reliable way within VSCodium to detect when an installed extension is behind its Microsoft Marketplace counterpart without switching galleries?