logo

microsoft/winget-cli

WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API...

Owned by Microsoft

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

microsoft/winget-cli has 26k+ stars and 1.5k+ forks on GitHub, is written in C++, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 26 minutes ago
Type:CLI ToolCategory(s):Build Systems & Package ManagersDeveloper Tools
Added to GitGenius on September 2nd, 2026
Created on July 16th, 2019
Open Issues & Pull Requests: 1,310 (+0)
GitHub issues: Enabled
Number of forks: 1,814
Total Stargazers: 26,505 (+0)
Total Subscribers: 342 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.1 hours
Mean response time: 48.9 days
90th percentile: 95.1 days
Tracked items: 1,822

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

7 people 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 four opened in the past year never receives a reply. 83% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "PowerShell" is answered fastest, typically in about 4 hours, while "Area-Output" waits about 3 days. 58% of tracked open issues have had no activity in three months. Only 45% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,262
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 943 days
Stale 30+ days: 1,227
Stale 90+ days: 1,048

Recent activity

Opened in 7 days: 1
Closed in 7 days: 1
Comments in 7 days: 2
Events in 7 days: 3

Top labels

  • Issue-Bug (950)
  • Issue-Feature (908)
  • Command-Upgrade (145)
  • PowerShell (121)
  • Area-External (119)
  • Resolution-Duplicate (107)
  • Command-Install (98)
  • Issue-Docs (95)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

WinGet is the Windows Package Manager, a command-line tool and API for discovering, installing, and managing software on Windows systems.

WinGet addresses the fragmentation of software installation on Windows by providing a unified package manager similar to those found on Linux and macOS. The tool works by connecting to package sources—primarily the Microsoft Store and the WinGet community repository—allowing users to search for, install, update, and remove applications through a single command-line interface. It also exposes its functionality through a PowerShell module and a COM API, enabling integration into scripts and other applications.

Developers and system administrators managing Windows environments should consider WinGet if they need to automate software deployment or want to reduce reliance on manual installers and vendor-specific update mechanisms. The tool suits organizations looking to standardize package management across Windows machines. It requires Windows 10 build 1809 or later, Windows 11, or Windows Server 2025, with experimental support for Windows Server 2019 and 2022. The primary distribution method is through the Microsoft Store's App Installer package, though development releases are available from GitHub and through the PowerShell module.

The project maintains active development with regular releases published both through the Microsoft Store and GitHub. The codebase is written in C++ and accepts community contributions. The tool includes an experimental features system that allows users to test upcoming functionality, and the project maintains comprehensive documentation including troubleshooting guides for common installation issues.