PAGES
← all tools
◆ Patch Management

Windows Package Manager

v1.29.380 open-source

Free plan: not checked yet · Open source: yes

Windows Package Manager (WinGet) is a command-line tool that lets users discover, install, upgrade, remove, and configure applications on Windows.

What you can do now

Checking Plays…

Summary

Windows Package Manager is an open-source package-manager for Windows that manages software installation, upgrading, and configuration via a command-line tool. It runs as a command-line tool and is intended for developers, Independent Software Vendors, and enterprise organizations looking to automate setup. Its documentation positions it alongside other package managers by providing functionality to write repeatable machine setup instructions using PowerShell Desired State Configuration in combination with YAML. The tool currently shows activity with 248 commits in the last year.

Windows Package Manager (WinGet) is a command-line tool that lets users discover, install, upgrade, remove, and configure applications on Windows.

How Windows Package Manager helps

Which packages are available on the system?

Lists packages from configured sources, such as the Microsoft Store and the community repository.

How do I automate setting up a device environment to ensure repeatable machine setup?

Creates a single command using a combination of PowerShell Desired State Configuration and YAML instructions.

Which tools and applications are needed for a specific project's prerequisites?

Supports developers specifying required packages and letting the package manager follow those declarative instructions to install and configure the tools.

How do I see a detailed list of installed packages?

Provides an option to display verbose package information beyond a simple table format.

What is the current operational configuration of my machine regarding package management?

Supports exporting current device settings, including package configurations and DSC settings, to a file.

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities

Built from Windows Package Manager's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What Windows Package Manager offers you

  • Command-line interface3
  • PowerShell script execution1

All capabilities 4 capabilities
Client configuration and diagnostics Displays client information, active policies, and available experimental features to help users understand and configure the tool. 2 other sources
Package discovery and search Lets users search for and browse available software packages from the command line. 2 other sources

Also counts toward: Command-line interface

Package installation Installs software packages by name or ID from the command line. 2 other sources

Also counts toward: Command-line interface

Client repair Repairs a broken or misconfigured WinGet installation. 1 other source

Also counts toward: Command-line interface, PowerShell script execution

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Windows Package Manager, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Windows Package Manager puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Commercials

pricing & packaging history · Microsoft vendor page

16 readings of Microsoft's pricing page since Mar 2022, with 3 relaunches of its plan lineup — each one dated, compared with the reading before it, and explained for someone buying the tool.

Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.

See plans →

Website history

microsoft.com, every change

Microsoft's home page and 46 more pages as they looked each month from October 2021 to November 2026: 1535 renders, 343 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Releases

Show

32 entries

  1. September 20261
  2. August 20261
  3. June 20261
  4. April 20261
  5. February 20262
  6. January 20261
  7. December 20251
  8. October 20251
  9. September 20251
  10. July 20251
  11. June 20251
  12. February 20251
  13. November 20241
  14. October 20241
  15. June 20241
  16. February 20241
  17. December 20232
  18. November 20231
  19. October 20231
  20. September 20233
  21. June 20231
  22. May 20231
  23. January 20231
  24. July 20221
  25. February 20221
  26. August 20201
  27. July 20201
  28. May 20201
    Show

    32 entries

    Project health

    Issue, contributor and maintainer activity in microsoft/winget-cli, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors not measured distinct committers, last 12 months
    2. Maintainers not measured core set, last 12 months
    3. Bus factor not measured committers behind half the commits
    4. Community-filed 85% of issues opened, last 12 months
    5. Median time to close 57 days first maintainer reply 24 hours
    6. Open backlog 1,268 of 3,482 issues ever filed
    1. Issues opened / month 27 · 0 communitymaintainers
    2. Open backlog 1,268
    3. Contributors / month not measured
    4. Commits / month not measured
    5. Stars not measured
    Issue themes, last 12 months
    • bugs 51%
    • features 37%
    • docs 5%
    • other 7%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.