Skip to content

Guide · Open source

How to use winget-pkgs: the Windows Package Manager manifest repo

Updated · written with AI from the project's own documentation and checked against our catalogue data

winget-pkgs is the GitHub repository that holds the manifest files for the default source of the Windows Package Manager, the command-line client for installing Windows software. This guide explains what the repository contains, how to get a local copy, and how to contribute manifests if you maintain or publish a Windows application. It is aimed at readers who want a clear picture of the repo's role, not at people looking for an app to download.

WinGetmicrosoft/winget-pkgs · ★ 11.3k · MIT

Quick start

  1. 1Decide what you need. Use this repository if you want to read or contribute manifests for the default Windows Package Manager source. If you only want an app, the repository does not contain the app itself.
  2. 2Clone the repository. Run git clone https://github.com/microsoft/winget-pkgs to get a local copy of the manifests.
  3. 3Read the documentation. Open the overview in doc/README.md and follow the topics on authoring and testing a manifest.
  4. 4Check your installer type. Confirm your installer is MSIX, MSI, APPX, MSIXBundle, APPXBundle or .exe. Script-based installers are not currently supported.
  5. 5Follow the first-contribution checklist. If this is your first contribution, use doc/FirstContribution.md before you submit.
  6. 6Submit and sign the CLA. Submit your manifest through a pull request, then follow the CLA bot's instructions if it asks for one.

What winget-pkgs contains

The repository stores manifest files, not the applications themselves. Each manifest describes an application, where its installer is located, and how to install it. The Windows Package Manager client reads these manifests from its default source.

Anyone can submit manifests for applications they want listed. The README encourages submissions for your favorite application.

  • Stores metadata and installer locations, not the installers or apps
  • Serves as the default package source for the Windows Package Manager client

Clone the repository

To get a local copy of the repository, run the clone command from the README. The source does not list other prerequisites.

git clone https://github.com/microsoft/winget-pkgs

Know which installer types are accepted

The README states that installers must currently be MSIX, MSI, APPX, MSIXBundle, APPXBundle, or .exe application installers. Font files (.ttf, .ttc, .otf, .otc, and .fnt) are also supported, although community submissions for fonts are not yet being accepted.

Script-based installers are not currently supported. If your application ships only as a script, it cannot be listed in this source.

  • Accepted: MSIX, MSI, APPX, MSIXBundle, APPXBundle, .exe
  • Font files are supported, but community submissions for them are not being accepted yet
  • Not accepted: script-based installers

Contribute a manifest or request a package

The README links to documentation on authoring a manifest, testing a manifest, the first-time contributor checklist, and submitting a manifest. You can also open an issue to request a new package or a new package version.

Most contributions require agreeing to a Contributor License Agreement (CLA). When you open a pull request, a CLA bot determines whether you need to provide one and comments on the PR. You only need to do this once across all Microsoft repositories that use the CLA.

  • Authoring a manifest and testing a manifest are covered in doc/README.md
  • First-time contributors can follow doc/FirstContribution.md
  • New packages and new versions are requested through doc/Issues.md

Use private repositories for private hosting

If you need private package hosting, the README points to a separate document on private repositories rather than this community source. The WinGet client itself is an open source project located in a separate repository.

What people use it for

  • Windows users who want to install apps from the command line using winget
  • Developers publishing a Windows application to the default winget source
  • Contributors maintaining manifests for existing Windows apps
  • Requesting a new package or a new package version through an issue

Frequently asked questions

Is winget-pkgs the same as the winget app?

No. The winget-pkgs repository holds manifest files for the default source. The Windows Package Manager client is a separate open source project in the microsoft/winget-cli repository.

Does winget-pkgs contain the actual applications?

No. The repository stores metadata that describes each application, where its installer is located and how to install it.

Can I install a script-based app through winget-pkgs?

Not currently. The README states that script-based installers are not supported. Installers must be MSIX, MSI, APPX, MSIXBundle, APPXBundle or .exe.

Do I need to sign anything to contribute?

Most contributions require agreeing to a Contributor License Agreement. A CLA bot checks your pull request and tells you what to do. You only need to sign once across Microsoft repositories that use the CLA.

How do I host private packages instead?

The README points to a separate document on private repositories that offer private WinGet package hosting. The community repository is not intended for private hosting.

How does winget-pkgs compare to Chocolatey or Scoop?

Comparable projects include the Chocolatey Community Repository and the Scoop Extras bucket. This source does not describe its comparison to them, so check each project's documentation to see which fits your workflow.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

winget-pkgs suits Windows users who want the default winget catalogue and developers or maintainers who want their app listed there. It is not a download site for apps and it does not accept script-based installers, so teams needing private hosting should look at the private repositories option or a comparable project such as Chocolatey or Scoop.

Install options & downloads