OSS TanbouSign in with GitHub

search, install, and update Windows packages through a CLI, PowerShell, and COM API

About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
26,478
Primary language
C++
License
MIT
Repository last updated
Oct 2, 2026
On this page

Overview

Windows Package Manager (WinGet) is Microsoft’s client for discovering, installing, and updating Windows applications from configured sources such as the community repository and Microsoft Store. The project also provides PowerShell modules and a COM API.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Address packages by ID for repeatable setup and upgrades

Commands such as winget search, show, install, and upgrade let scripts select package IDs and sources instead of relying on display names.

Sources: [1]

Best fit

Fits teams standardizing Windows development and evaluation machines

It replaces manual installer discovery with commands against default or managed private REST sources, helping reduce drift across Windows workstations.

Sources: [1]

Before adoption

Review source policy, telemetry, and official-distribution boundaries

Group Policy can change sources and available behavior, and the README recommends winget --info to inspect policy. It also documents usage and diagnostic telemetry and warns that self-built clients receive less support than official distribution channels.

Sources: [1]

Official sources

  1. [1]Windows Package Manager CLI v1.29.380 README(2026-10-04)
  2. [2]Windows Package Manager CLI v1.29.380 release(2026-10-04)
  3. [3]Windows Package Manager CLI v1.29.380 license(2026-10-04)
Supplemental curator note

Start with read-only searches and source inspection, then review Group Policy, source configuration, and installer trust before installing or upgrading packages.

Try it in 3 steps

  1. 1

    Check the client version

    Confirm the WinGet client available on the Windows machine.

    winget --version
  2. 2

    Inspect sources and policy information

    Review sources, paths, and Group Policy effects before any installation.

    winget --info && winget source list
  3. 3

    Run an exact read-only package search

    Confirm the exact package ID and source without launching an installer.

    winget search --id Microsoft.PowerShell --exact
Check the official README

Growth

Growth trends · Last 30 days

26,478 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
29
Open PRs
41

Development activity is still being collected.

Built with

Categories and tags

GitHub data

GitHub dataView detailed GitHub data

GitHub Topics

  • windows
  • package-manager
  • winget
  • command-line
Stars
26,478
Forks
1,808
Watchers
340
Open issues
1,259
Contributors
127
Owner type
Organization
Primary language
C++
License
MIT
Repository last updated
Oct 2, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?