winget source edit winget-font
winget source edit winget-font
winget mcp
winget search font -s winget-font
winget search font -s winget-font
winget mcp
winget search font -s winget-font
winget mcp
winget search font -s winget-font
winget font list
{
"$schema" "https://aka.ms/winget-settings.schema.json",
"experimentalFeatures": {
"fonts": true
}
}
{
"$schema": "https://aka.ms/winget-settings.schema.json",
"visual": {
"enableSixels": true,
"progressBar": "sixel"
}
}
{
"$schema": "https://aka.ms/winget-settings.schema.json",
"experimentalFeatures": {
"configureSelfElevate": true
}
}
winget --info
winget features
What you can do now
Checking Plays…
Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed 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.
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.
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.
+Client configuration and diagnosticsNot checked yet · Date unknownDisplays client information, active policies, and available experimental features to help users understand and configure the tool.2 other sources▸
+Package discovery and searchNot checked yet · Date unknownLets users search for and browse available software packages from the command line.2 other sources▸
Also counts toward: Command-line interface
+Package installationNot checked yet · Date unknownInstalls software packages by name or ID from the command line.2 other sources▸
Also counts toward: Command-line interface
+Client repairNot checked yet · Date unknownRepairs 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.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian 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.
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.
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.
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date.
A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product.
Readings that failed to show any plans are left out rather than read as a change.
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.
← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Brand changes
Each row is a name, owner or logo change we've confirmed. The dates are the last capture before it and the first one after. A new page design on its own isn't counted. Spot one that's wrong? Use “Not a rebrand” on its row.
We spotted these but haven't confirmed them yet, so they aren't counted above.
Releases
Show
32 entries
No entries match these filters.
September 20261
August 20261
June 20261
April 20261
February 20262
January 20261
December 20251
October 20251
September 20251
July 20251
June 20251
February 20251
November 20241
October 20241
June 20241
February 20241
December 20232
November 20231
October 20231
September 20233
June 20231
May 20231
January 20231
July 20221
February 20221
August 20201
July 20201
May 20201
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.
Contributorsnot measureddistinct committers, last 12 months
Maintainersnot measuredcore set, last 12 months
Bus factornot measuredcommitters behind half the commits
Community-filed85%of issues opened, last 12 months
Median time to close57 daysfirst maintainer reply 24 hours
Open backlog1,268of 3,482 issues ever filed
Issues opened / month27 · 0communitymaintainers
Open backlog1,268
Contributors / monthnot measured
Commits / monthnot measured
Starsnot 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.
Copy this, send it to your AI assistant, then come back with its reply.
Nothing is sent from here. You paste the reply in the next step.
1 Copy
2 Paste
3 Confirm
Paste the reply
One tool per line is best. Versions are optional, and any format works. Names we don’t track are sent to us, without versions, so we can consider adding them.