microsoft/vcpkg

C++ Library Manager for Windows, Linux, and MacOS

Owned by Microsoft

View on GitHub ↗Jump to charts ↓Open shareable report →

microsoft/vcpkg has 27k+ stars and 7.5k+ forks on GitHub, is written in CMake, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 2nd, 2026
Created on September 15th, 2016
Open Issues & Pull Requests: 1,099 (+1)
GitHub issues: Enabled
Number of forks: 7,760
Total Stargazers: 27,525 (+1)
Total Subscribers: 440 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.9 hours
Mean response time: 9.3 days
90th percentile: 10.0 days
Tracked items: 4,133

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "requires:repro" is answered fastest, typically in about 2 hours, while "info:good-first-issue" waits about 14 days. 54% of tracked open issues have had no activity in three months. 61% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 716
New in 7 days: 25
Closed in 7 days: 17
Avg open age: 502 days
Stale 30+ days: 622
Stale 90+ days: 448

Recent activity

Opened in 7 days: 21
Closed in 7 days: 16
Comments in 7 days: 27
Events in 7 days: 61

Top labels

  • Stale (1,876)
  • category:port-bug (773)
  • category:question (672)
  • category:port-update (668)
  • requires:repro (379)
  • category:port-feature (327)
  • category:community-triplet (278)
  • category:new-port (265)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

vcpkg is a C/C++ package manager for Windows, Linux, and macOS maintained by Microsoft and the C++ community.

The tool addresses the challenge of managing C/C++ library dependencies across different platforms and build systems. It works by maintaining a registry of open-source libraries that developers can declare as dependencies either through a manifest file for their project or via command-line installation. vcpkg integrates with popular build systems including CMake, MSBuild, and others, and works with Visual Studio, Visual Studio Code, CLion, and Qt Creator. The tool itself is written in C++ with CMake scripts, designed specifically to handle the dependency management pain points unique to C/C++ development.

Developers should choose vcpkg if they work with C/C++ projects on Windows, macOS, or Linux and want a unified approach to managing library dependencies across these platforms. It suits projects using CMake, MSBuild, or other build systems, and works regardless of which editor or IDE you prefer. The tool provides both manifest-based dependency declaration for reproducible builds and classic command-line package installation modes. If a required library is not in the registry, the README indicates that developers can either open an issue or contribute the package themselves through the documented packaging process.

The project maintains active engagement with its community through contribution pathways including a packaging tutorial and maintainer guide. Development activity shows consistent evolution of the tool and ecosystem with ongoing refinement of features and integrations. The project accepts community contributions and provides structured documentation for both adding new packages to the registry and maintaining existing ones.