pkg.soopen package index

cask

vscodium mit Homebrew Cask installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für vscodium in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrew Caskverifiziert · 100%
brew install --cask vscodium

local Homebrew cask metadata

Überblick

Paketzusammenfassung

Binary releases of VS Code without MS branding/telemetry/licensing

Befehle und Aliase

  • codium

Verlauf

Projektgeschichte und Nutzung

VSCodium is a community build and release system for freely licensed Visual Studio Code binaries. It removes Microsoft branding and configured telemetry and supplies desktop packages for major operating systems.

Projektgeschichte

The VSCodium project began in 2018 as automation for building Microsoft's MIT-licensed vscode source into community-distributed binaries. The project emphasizes that it is a build-and-release system rather than a source-code fork.

Its scripts fetch upstream VS Code, apply community product configuration and branding, disable telemetry, build platform packages, and publish the resulting binaries. This model allows releases to follow upstream VS Code closely while keeping VSCodium-specific changes relatively small.

Adoptionsgeschichte

VSCodium became a prominent way to obtain the open-source VS Code codebase as ready-made binaries without Microsoft's product branding, proprietary release license, or configured telemetry endpoints.

Its distribution broadened from GitHub releases to Homebrew, Windows package managers, Snap, Flatpak, Arch packages, and an apt/rpm repository. VSCodium uses Open VSX as its default extension registry because Microsoft Marketplace terms restrict Marketplace offerings to Visual Studio products and services.

Wie es verwendet wird

Users install VSCodium as a general-purpose graphical code editor and IDE platform. Most VS Code workflows and settings carry over, but extensions come from Open VSX by default and some Microsoft-restricted extensions may be unavailable or incompatible.

Warum Paket-Nerds sich dafür interessieren

VSCodium makes the distinction between an open-source codebase and vendor-produced binaries unusually visible. It is a practical case study in reproducible downstream builds, branding, telemetry defaults, extension-registry policy, and the licensing consequences of repackaging an upstream editor.

Zeitleiste

  • 2018: The VSCodium project and its MIT-licensed build scripts were established.
  • 2018: Community apt and rpm packaging work began alongside the GitHub releases.
  • VSCodium subsequently gained Homebrew, WinGet, Chocolatey, Scoop, Snap, Flatpak, and Arch-oriented installation paths.

Related projects

  • VSCodium is built from Microsoft's vscode source repository. It uses Open VSX for extensions by default and has an Insiders channel corresponding to upstream prerelease builds.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für vscodium wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
~/.config/VSCodium/User/settings.json~/.config/VSCodium/User/keybindings.json
macOS
~/Library/Application Support/VSCodium/User/settings.json~/Library/Application Support/VSCodium/User/keybindings.json
Windows
%APPDATA%\VSCodium\User\settings.json%APPDATA%\VSCodium\User\keybindings.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
codiumBinärdateiHomebrew-Cask-Binärdateicodium

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-11-04
Manager-Version1.143.17232
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/VSCodium/vscodium

Installationsmetadaten

Paketmetadaten

Paketschlüsselcask:vscodium
Version1.143.17232
PaketmanagerHomebrew Cask
Paketmanager-Seitehttps://formulae.brew.sh/cask/vscodium
Homepagehttps://github.com/VSCodium/vscodium
Repositoryhttps://github.com/VSCodium/vscodium
Quellarchivhttps://github.com/VSCodium/vscodium/releases/download/1.143.17232/VSCodium-darwin-arm64-1.143.17232.zip
SHA-256ade8f5e0ebf47e5ea9e2478844f150c68e43def192b6f8be05d0329d25ec0917
Bottlenicht erfasst
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokenvscodium
Names
  • VSCodium
Artifacts
Auto Updatesyes
Deprecatedno
Disabledno

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment