Library / SDK
microsoft/winget-pkgs avatar
microsoft/winget-pkgs

winget-pkgs: The manifest repository that decides what Windows Package Manager can install

The Microsoft community Windows Package Manager manifest repository

11,327 stars12,565 forksUnknownMIT

At a glance

What is it?
Microsoft's winget-pkgs is the community manifest store behind the default winget source. It defines which installers are accepted, how they are described, and who can add them.
Who is it for?
Adopt winget-pkgs if you are a software vendor who wants your installer available through the default winget source, or if you use winget and want to know why some packages appear and others do not. Do not adopt it if you need script-based installers, private hosting, or control over which packages are listed; the README explicitly excludes script installers and points to separate private repository documentation.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • microsoft/winget-pkgs11,327 ★ · +337
Star history
Repository2026-08-212026-11-15
microsoft/winget-pkgs11k11.3k

337 Stars in the last 86 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

What this repository actually is

winget-pkgs is not a package manager and not an installer. It is a collection of manifest files that describe how to install applications through the Windows Package Manager client. The README calls it the default source for that client. When you run winget install on a fresh Windows machine, the results come from manifests stored here. The repository is the middle layer between software authors and the winget command-line tool. It solves a specific problem: without a central, versioned description of each installer, the client would have no reliable way to know what to download, what checksum to expect, or what installer type to run. The intended audience is twofold. End users benefit indirectly because more manifests mean more installable software. The direct contributors are application vendors and package maintainers who want their software listed in the default source.

The manifest mechanism and its constraints

Each manifest is a structured description of a package version. The README does not show a full manifest schema, but it does list the supported installer formats: MSIX, MSI, APPX, MSIXBundle, APPXBundle, and .exe application installers. Font files are also supported, though community submissions for fonts are not accepted at this time. Script-based installers are explicitly unsupported. That is a hard boundary. A package that only ships as a .bat or .ps1 installer cannot be submitted here. The mechanism works because the winget client reads these manifests, matches the requested package name and version, and then executes the described installer. The repository itself does not host the installer binaries. It only holds the metadata that points to them.

How to get a package in: the contribution path

The README points to a first-time contributor checklist and a detailed overview document, but it gives enough to sketch the path. You start by authoring a manifest following the schema described in doc/README.md. Then you test it locally. The README references a testing topic but does not give the command. After testing, you submit a pull request. A bot checks whether you have signed the Microsoft Contributor License Agreement. If not, the bot decorates the PR with instructions. You only sign once across all Microsoft repositories. The submission must not link to third-party materials that violate that party's rights or applicable law. That last point matters for vendors who redistribute code they do not own. The actual commands for validation are in the documentation files, not in the README, so a first-time contributor must read doc/FirstContribution.md before doing anything.

A real limitation: the default source is a bottleneck

Because winget-pkgs is the default source, its rules apply to everyone using winget without a custom configuration. The README explicitly says script-based installers are not supported. That excludes a large class of tools that only distribute via PowerShell scripts or batch files. It also excludes fonts from community submissions, even though the format is supported internally. If your application ships only as a script or a font, this repository is the wrong place to publish it. Another limitation is the review process. Every manifest goes through a pull request. There is no automated self-service path mentioned in the README. That means updates to existing packages also require PRs, which can delay version bumps. The README does not state review times. For a tool that needs same-day updates, this is a friction point.

Private repositories as the alternative

The README points to a separate document for private repositories: doc/private/README.md. That is the alternative for teams that do not want to depend on the public community repository. Private hosting lets an organization control which packages appear, which versions are available, and how installers are vetted. The approach differs fundamentally: winget-pkgs is a public, community-curated collection where anyone can submit a manifest, subject to CLA and code of conduct. The README does not describe the private mechanism in detail, but the existence of that document shows that Microsoft treats private hosting as a distinct supported path.

Maintenance cost and licence implications

The repository is licensed under MIT, which means the manifest files themselves are permissively licensed. That is a low barrier for downstream use. The contribution process, however, carries a heavier cost. Every manifest update is a pull request that must pass the CLA bot and presumably human review. For a vendor maintaining a single package, that is manageable. For an organization managing dozens of packages, the overhead multiplies. The README says nothing about automated update pipelines or scheduled version refreshes. There is no mention of a bot that submits updates on your behalf. The code of conduct and CLA are standard Microsoft open source requirements. The practical maintenance cost is not the licence but the ongoing PR workflow.

Who should adopt it and what to verify first

Adopt winget-pkgs if you are a vendor with an MSI, MSIX, APPX, or .exe installer and you want your software reachable through the default winget source. Do not adopt it if your installer is script-based, if you need to control which versions are listed, or if you cannot sign the CLA. Before submitting, verify three things. First, confirm your installer type is in the allowed list. Second, read doc/FirstContribution.md and doc/README.md to learn the exact manifest schema and testing commands. Third, check that your third-party dependencies do not violate their own licences, as the README warns against submissions that violate third-party rights. The repository is a gate, not a guarantee. It only works if contributors follow its rules.

Editorial conclusion

Adopt winget-pkgs if you are a software vendor who wants your installer available through the default winget source, or if you use winget and want to know why some packages appear and others do not. Do not adopt it if you need script-based installers, private hosting, or control over which packages are listed; the README explicitly excludes script installers and points to separate private repository documentation. Before submitting, verify that your installer is one of the allowed types (MSIX, MSI, APPX, MSIXBundle, APPXBundle, or .exe) and that you can comply with the Contributor License Agreement. The repository is the gatekeeper for the default source, so its rules are your rules.

Frequently asked questions

What packages are available on winget?

The default source is whatever the manifests/ tree holds on the master branch, and the root README publishes no index or count of it. The README constrains what can appear there: installers must be MSIX, MSI, APPX, MSIXBundle, APPXBundle or .exe, with font files supported but not currently accepted as community submissions, and script-based installers not supported at all.

How do I list all available packages in winget?

The root README gives no client command for it. It points instead at microsoft/winget-cli, the open source command-line client, and the set of packages is the manifest files in this repository on the master branch, with no GitHub releases to pin a version against.

Is it safe to use winget?

The client is a separate open source Microsoft project, microsoft/winget-cli, and this repository is only its manifest source. The safeguards documented here are procedural: a Contributor License Agreement checked by a bot, an accepted installer format list, and a rule that you may not submit links to third-party materials when the third party prohibits it.

What is the best package manager for Windows?

This repository cannot answer that, since it is the manifest source for one client rather than a comparison. It describes the Windows Package Manager as an open source client designed for command-line usage, hosted at microsoft/winget-cli, and says nothing about how it compares to other Windows package managers.

Official sources

  1. Official README
  2. Project repository
  3. README
  4. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/microsoft-winget-pkgs.svg)](https://hysenlabs.com/projects/microsoft-winget-pkgs)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/microsoft-winget-pkgs.svg)](https://hysenlabs.com/projects/microsoft-winget-pkgs)

Was this useful?