microsoft/winget-pkgs

The Microsoft community Windows Package Manager manifest repository

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 22 seconds ago
Added to GitGenius on August 8th, 2026
Created on July 16th, 2019
Open Issues & Pull Requests: 4,031 (+0)
GitHub issues: Enabled
Number of forks: 9,782
Total Stargazers: 11,098 (+0)
Total Subscribers: 120 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.6 hours
Mean response time: 15.4 days
90th percentile: 7.8 days
Tracked items: 6,390

How this project is maintained

About 8% of issues opened in the past year have never received a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Error-Hash-Mismatch" is answered fastest, typically in under an hour, while "Package-Request" waits about 29 hours. 48% of tracked open issues have had no activity in three months. 80% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,320
New in 7 days: 63
Closed in 7 days: 38
Avg open age: 575 days
Stale 30+ days: 1,175
Stale 90+ days: 993

Recent activity

Opened in 7 days: 59
Closed in 7 days: 35
Comments in 7 days: 10
Events in 7 days: 95

Top labels

  • Package-Update (3,022)
  • Package-Request (1,666)
  • Issue-Bug (1,306)
  • In-PR (1,212)
  • Help-Wanted (1,040)
  • Error-Hash-Mismatch (1,012)
  • Needs-Triage (854)
  • Issue-Feature (558)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The microsoft/winget-pkgs repository serves as the official community-maintained manifest repository for the Windows Package Manager, Microsoft's command-line package management tool. This repository contains the manifest files that define how applications are packaged and distributed through the Windows Package Manager default source, making it the central hub where community members contribute package definitions for their favorite applications.

The repository accepts manifest submissions for applications packaged in specific installer formats: MSIX, MSI, APPX, MSIXBundle, APPXBundle, and .exe installers. Additionally, font files with extensions .ttf, .ttc, .otf, .otc, and .fnt are supported, though community submissions for fonts are not currently being accepted. Script-based installers are explicitly not supported at this time. This format restriction ensures consistency and security across the package ecosystem.

The repository provides comprehensive documentation to guide contributors through the entire process of participating. The documentation covers authoring manifests, testing them before submission, and the complete submission workflow. For first-time contributors, there is a dedicated checklist to ensure they understand the requirements and process. The repository also facilitates community requests through its issue tracking system, allowing users to request new packages or new versions of existing packages through a structured process.

Contributing to this repository requires agreement to Microsoft's Contributor License Agreement, which is automatically enforced through a CLA bot that reviews pull requests. The project has adopted the Microsoft Open Source Code of Conduct, establishing standards for respectful and professional community interaction. Contributors are explicitly prohibited from submitting manifests that link to third-party materials in violation of applicable third-party rights or terms.

The Windows Package Manager itself is an open-source client tool designed specifically for command-line usage, with its source code maintained in a separate repository. For organizations seeking private package hosting solutions, the repository documentation references private repository options that enable private WinGet package management.

The repository is tagged with the Hacktoberfest topic, indicating its participation in community contribution initiatives. The manifest-based approach allows for decentralized contribution while maintaining centralized quality control through the submission and review process. By hosting manifests rather than binaries, the repository keeps file sizes manageable while providing a single source of truth for how applications should be packaged and installed through the Windows Package Manager ecosystem. This structure enables rapid community participation in expanding the available packages while Microsoft maintains oversight of the manifest standards and quality.