Automic VaultAutomic Vault

brew

code-cli mit Homebrew, Nix, pacman installieren

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

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install code-cli

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#code

nixpkgs package indexes · pkgs/by-name/co/code/package.nix · Quelle: api.github.com

Arch Linux pacmanverifiziert · 92%
sudo pacman -S code

Arch Linux sync databases · code · Quelle: geo.mirror.pkgbuild.com

Überblick

Paketzusammenfassung

Command-line interface built-in Visual Studio Code

Befehle und Aliase

  • code

Verlauf

Projektgeschichte und Nutzung

The Visual Studio Code CLI is the command-line surface of VS Code, exposed as the `code` command. It lets users launch the editor, open files and folders, manage extensions, inspect status, and create remote tunnels from a terminal.

Projektgeschichte

VS Code was announced in 2015 as Microsoft's cross-platform editor. Later that year the November 2015 Beta release made the Code OSS project open source and added extension support. The `code` command became part of the product's developer workflow: the official CLI docs describe it as built in and document editor launch, file navigation, extension management, chat, diagnostics, and tunneling.

Adoptionsgeschichte

Microsoft's 1.0 announcement reported 2 million installs and more than 500,000 monthly active developers by April 2016. The CLI followed VS Code's adoption because `code .` became the normal bridge between shell workflows and the editor. The input also records package-manager distribution for the CLI through Homebrew, Nix, and pacman.

Wie es verwendet wird

Common usage includes `code .` to open the current directory, file arguments to open or create files, `--install-extension` and `--list-extensions` for extension workflows, `--user-data-dir` for isolated instances, and `code tunnel` for remote tunnel setup.

Warum Paket-Nerds sich dafür interessieren

For package-manager users, `code-cli` matters because it splits the terminal command from the desktop app story. A working `code` executable is what lets editors participate in Unix-style workflows: scripts can open files, shells can jump into projects, and remote machines can expose VS Code access without starting from a GUI installer.

Zeitleiste

  • 2015: Visual Studio Code announced at Build.
  • 2015: November Beta made VS Code open source and added extensions.
  • 2016: Visual Studio Code 1.0 released with reported 2 million installs and 500,000 monthly active developers.
  • 2026: Official CLI docs cover built-in `code` command workflows, chat subcommands, and remote tunnels.

Related projects

  • Related projects and surfaces include the microsoft/vscode Code OSS repository, the VS Code desktop product, VS Code Insiders, Remote Tunnels, the extension marketplace, and downstream open-source builds such as Code OSS packages.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für code-cli wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-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.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 2 Build-Abhängigkeiten.

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/Code/User/settings.json.vscode/settings.json
macOS
~/Library/Application Support/Code/User/settings.json.vscode/settings.json
Windows
%APPDATA%\Code\User\settings.json.vscode\settings.json

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
codecliglobales Executable

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-07-25
Manager-Version1.130.0
Manager aktualisiert2026-07-22
lokale DatenOK
Upstreamaktuell
neueste erkannte Version1.130.0

https://github.com/microsoft/vscode

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:code-cli
Version1.130.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/code-cli
Homepagehttps://code.visualstudio.com
Repositoryhttps://github.com/microsoft/vscode
Upstream-Dokumentationhttps://code.visualstudio.com/docs/configure/settings
LizenzMIT
Quellarchivhttps://github.com/microsoft/vscode/archive/refs/tags/1.130.0.tar.gz
Zuletzt aktualisiert2026-07-22T21:00:40Z
Pulseupdated
Abhängigkeitenopenssl@4
Build-Abhängigkeitenpkgconf, rust
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecode-cli
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix92%

code

nix profile install nixpkgs#code
  • installed executable or alias match
  • Abgeglichen nach: Code
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/co/code/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
pacman92%

code 1.123.0-1

The Open Source build of Visual Studio Code (vscode) editor

https://github.com/microsoft/vscode

sudo pacman -S code
  • License: MIT
  • Architecture: x86_64
  • 5 Abhängigkeiten
  • 1 stellt bereit
  • 3 optionale Abhängigkeiten
  • installed executable or alias match
  • Abgeglichen nach: Code
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: code from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Verwandte Tools

  • openssl@4Runtime dependency declared by Homebrew.
  • pkgconfBuild dependency declared by Homebrew.
  • rustBuild dependency declared by Homebrew.
  • code-serverPackage names and metadata indicate a similar tool family. Shared terms: cli, code, developer, developer-tools, vscode.

Gleicher Workflow

  • ansible-language-serverShares av.db curated category or tags: cli, developer-tools, editor, vscode.
  • neovideShares av.db curated category or tags: cli, developer-tools, editor.
  • neovimShares av.db curated category or tags: cli, developer-tools, editor.
  • neovim-qtShares av.db curated category or tags: cli, developer-tools, editor.
  • evil-helixShares av.db curated category or tags: cli, developer-tools, editor.
  • neovim-remoteShares av.db curated category or tags: cli, developer-tools, editor.

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

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment