# vsce mit Homebrew, Nix installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für vsce in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:vsce ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install vsce ``` Evidenz: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#vsce ``` Evidenz: nixpkgs package indexes: pkgs/by-name/vs/vsce/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Paketfakten - **Paketschlüssel:** brew:vsce - **Paketmanager:** Homebrew - **Version:** 3.9.2 - **Quellzusammenfassung:** Tool for packaging, publishing and managing VS Code extensions - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-06-03T23:08:04Z - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - vsce (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 3.9.2 ## Projektgeschichte und Nutzung @vscode/vsce is Microsoft's command-line tool for packaging, publishing, and managing Visual Studio Code extensions. It produces VSIX packages, publishes extensions to the Visual Studio Marketplace, and handles publisher-oriented operations such as metadata lookup and unpublishing. ### Projektgeschichte The VSCE repository was created in September 2015, the same year Visual Studio Code's extension ecosystem emerged publicly. The original npm package name was `vsce`, created in October 2015, and the CLI command remained `vsce` even after the package name later changed. In the November 2022 VS Code 1.74 release notes, Microsoft announced that the VS Code extension manager had been renamed from `vsce` to `@vscode/vsce`. The note called the rename a breaking change for library consumers, while preserving the command-line executable name and documenting installation with `npm install -g @vscode/vsce`. The official publishing documentation continues to put `vsce` at the center of extension release workflows: authors package a local extension into a `.vsix`, publish it to the Marketplace, and can also retrieve metadata, search, or unpublish through the CLI. The same documentation now also reflects Marketplace security constraints and the move toward Microsoft Entra ID based automated publishing as long-lived Azure DevOps PATs are retired. ### Adoptionsgeschichte VSCE's adoption is effectively tied to VS Code's extension marketplace. Because the Marketplace is the standard distribution channel for VS Code extensions, extension authors commonly use VSCE locally or in CI whenever they need to turn a `package.json`-based extension project into a publishable artifact. The npm registry records both the older `vsce` package and the newer scoped `@vscode/vsce` package. The older package is marked deprecated with guidance to install `@vscode/vsce`, while the scoped package continues to receive releases. ### Wie es verwendet wird A typical extension author works from an extension directory containing `package.json`, runs `vsce package` to create a VSIX, and runs `vsce publish` to publish to the Visual Studio Marketplace. The CLI also enforces Marketplace constraints, such as restrictions on untrusted SVG content and image URLs in README and CHANGELOG files. For package users, VSCE is the canonical bridge between a VS Code extension source tree and the Marketplace. It is not a language tool; it is release tooling for the VS Code extension ecosystem. ### Warum Paket-Nerds sich dafür interessieren VSCE is package-nerd-significant because it is the release valve for one of the largest editor-extension ecosystems. It encodes Marketplace rules into a CLI that can run on a maintainer laptop or in CI, making extension publication scriptable and repeatable. ### Zeitleiste - 2015: Microsoft creates the VSCE repository and publishes the original `vsce` npm package. - 2022: VS Code 1.74 announces the rename from `vsce` to `@vscode/vsce`; the CLI command remains `vsce`. - 2026: The official docs warn that global Azure DevOps PATs are retired on December 1, 2026, and recommend Entra ID based automated publishing. ### Related projects - VSCE is related to Visual Studio Code, the VS Code Extension Marketplace, VSIX packaging, Azure DevOps Marketplace services, extension signing, and VS Code extension CI workflows. ### Quellen - GitHub repository API metadata: https://api.github.com/repos/microsoft/vscode-vsce - Microsoft VSCE GitHub repository: https://github.com/microsoft/vscode-vsce - VS Code 1.74 release notes: https://code.visualstudio.com/updates/v1_74 - VS Code publishing documentation: https://code.visualstudio.com/api/working-with-extensions/publishing-extension - npm registry metadata for @vscode/vsce: https://registry.npmjs.org/@vscode/vsce - npm registry metadata for legacy vsce: https://registry.npmjs.org/vsce ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - narrow executable package without higher-risk signals ## 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 - Unix: package.json - Windows: package.json ## Andere Paketmanager-Einträge - Nix - vsce: normalized package name match | nixpkgs package indexes: pkgs/by-name/vs/vsce/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/vsce.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vsce.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph