Automic VaultAutomic Vault

brew

Installer vcpkg avec Homebrew, dnf, Nix, pacman, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de vcpkg pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install vcpkg

local Homebrew formula metadata

Windows

Scoopvérifié · 92%
scoop install main/vcpkg

Scoop official bucket manifest trees · bucket/vcpkg.json · Source: api.github.com

aperçu

Résumé du paquet

C++ Library Manager

Commandes et alias

  • vcpkg

historique

Historique du projet et usages

vcpkg is Microsoft's open-source C and C++ package manager, built around a curated ports registry, a command-line tool, and integration points for native build systems. It began as a way to make Windows C++ library consumption less painful, then grew into a cross-platform workflow for Windows, macOS, Linux, and multiple target triplets.

The project matters because it brought package-manager ergonomics to an ecosystem that historically depended on handwritten build instructions, vendored source trees, system packages, or project-specific CMake glue. Its package-nerd identity is the combination of source-built ports, reproducible baselines, triplets, binary caching, and manifest files checked into application repositories.

Historique du projet

The public Microsoft/vcpkg repository was created on 2016-09-15, matching Microsoft's later description of the September 2022 release as vcpkg's sixth anniversary. Early vcpkg centered on a shared installed tree and simple commands for acquiring C++ libraries; the maintained registry became the main social and technical object, with contributors adding and updating port recipes.

By 2020, vcpkg's implementation was being separated into the Microsoft/vcpkg-tool repository, whose GitHub metadata describes it as the components of the vcpkg binary. That split reflects the project's maturation from a scripts-and-ports repository into a package manager with an independently released tool and a fast-moving registry.

Historique d'adoption

Microsoft's C++ Team reported in October 2022 that vcpkg had passed 2,000 unique open-source libraries in its public registry, with over 10,000 available port versions, 95 contributors active during that release window, 4.8k forks, and 16.8k GitHub stars. On 2026-07-02, GitHub API metadata for Microsoft/vcpkg showed more than 27k stars and 7.6k forks, indicating continued adoption in the C++ tooling community.

The public vcpkg site describes a catalog of 2,849 open-source libraries, while Microsoft Learn material presents vcpkg as a free C/C++ package manager for acquiring and managing libraries and adding private libraries. The adoption story is therefore both public-registry growth and enterprise workflow growth: teams can pin baselines, use custom registries, and share binary caches in CI.

Modes d'utilisation

Modern vcpkg use is usually manifest mode: projects commit a vcpkg.json file declaring direct dependencies and, when needed, a vcpkg-configuration.json file for registries and baselines. Microsoft Learn describes manifest mode as the recommended workflow for most users, while classic mode remains available for installing packages directly into a vcpkg tree.

Package users care about triplets because vcpkg packages are built for a target configuration rather than merely downloaded as opaque archives. CI-heavy users care about binary caching, which Microsoft documents as a way to persist vcpkg-built binaries across clean build agents, including GitHub Actions workflows.

Pourquoi les passionnés de paquets s'y intéressent

vcpkg is significant because it treats C++ package management as a build-recipe and ABI problem instead of only a download problem. Ports can encode source retrieval and build steps, triplets encode target choices, manifests encode project dependencies, and baselines make dependency versions reviewable in source control.

For package maintainers, vcpkg also became a visible catalog of C and C++ library portability work. A working port is not just a version number; it is evidence that a library can be fetched, patched if necessary, configured, built, and tested across at least one supported target.

Chronologie

  • 2016-09-15: The Microsoft/vcpkg GitHub repository was created.
  • 2020-12-08: The Microsoft/vcpkg-tool repository was created for the vcpkg binary components.
  • 2022-10-06: Microsoft marked vcpkg's sixth anniversary and reported more than 2,000 unique libraries in the public registry.
  • 2024: Microsoft Learn continued positioning manifest mode as the recommended workflow for most users.
  • 2026-07-02: GitHub API metadata showed Microsoft/vcpkg with more than 27k stars and active pushes on the same day.

Related projects

  • vcpkg is commonly compared with Conan, system package managers, language-specific package managers, and project-local vendoring. Its closest internal companion is vcpkg-tool, the repository for the compiled tool that works with the main ports registry.
  • In CMake projects, vcpkg is often used through its toolchain integration, so its practical ecosystem overlaps heavily with CMake, MSBuild, Visual Studio, GitHub Actions, NuGet-style binary caches, and private source registries.

Sources

posture de sécurité

Niveau de risque : vert

library-like package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • library-like package without higher-risk signals

Signaux

  • metadata:library-like

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • S’installe avec 2 dépendances d’exécution.
  • Les métadonnées de compilation listent 2 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

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.

Unix
vcpkg.jsonvcpkg-configuration.json

exécutables

Exécutables installés

CommandeTypeExpositionNote
vcpkgcliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-10
version du gestionnaire2026-05-27
gestionnaire mis à jour2026-06-01
données localesOK
amontnot checked
dernière version détectéenon détecté

https://github.com/microsoft/vcpkg-tool

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:vcpkg
Version2026-05-27
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/vcpkg
Page d'accueilhttps://github.com/microsoft/vcpkg
Dépôthttps://github.com/microsoft/vcpkg
Docs amonthttps://learn.microsoft.com/en-us/vcpkg
LicenceMIT
Archive sourcehttps://github.com/microsoft/vcpkg-tool/archive/refs/tags/2026-05-27.tar.gz
Dernière mise à jour2026-06-01T19:50:20Z
Pulseupdated
Dépendancesfmt, ninja
Dépendances de compilationcmake, cmrc
Bibliothèques fournies par macOScurl
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré
PrécautionsThis formula provides only the `vcpkg` executable. To use vcpkg: git clone https://github.com/microsoft/vcpkg "$HOME/vcpkg" export VCPKG_ROOT="$HOME/vcpkg"

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

vcpkg

nix profile install nixpkgs#vcpkg
  • normalized package name match
  • Correspondance par : Vcpkg
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/vc/vcpkg/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
dnf95%

vcpkg 2026.04.08-1.fc45

C++ Library Manager

https://github.com/microsoft/vcpkg-tool

sudo dnf install vcpkg
  • License: MIT
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: vcpkg
  • 11 Dépendances
  • 2 fournit
  • normalized package name match
  • Correspondance par : Vcpkg
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: vcpkg from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst
pacman95%

vcpkg 2026.05.27-1

C++ library manager

https://vcpkg.io

sudo pacman -S vcpkg
  • License: MIT
  • Architecture: x86_64
  • 10 Dépendances
  • normalized package name match
  • Correspondance par : Vcpkg
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: vcpkg from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz
Scoop95%

main/vcpkg

scoop install main/vcpkg
  • normalized package name match
  • Correspondance par : Vcpkg
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/vcpkg.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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