Skip to content

microsoft/winget-command-not-found

View on GitHub ↗Related repositories →

WinGet Command Not Found is a PowerShell 7 module to help you install missing packages. With this module, you will be recommended relevant WinGet packages whenever an unrecognized command is entered.

active 2024-05-21 → 2026-09-16 (UTC)

Complete coverage27,291 / 27,294 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-25 (UTC)
Events
145
Pushes
10
Pull requests
13
Issues
29
Stars
40
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 849 days from 2024-05-21 to 2026-09-16. Pushes: 10 total, peak 2 in a day. Pull requests: 13 total, peak 3 in a day. Issues: 29 total, peak 5 in a day. Comments: 29 total, peak 3 in a day. Stars: 40 total, peak 6 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 40 stars here means stars gained during the window, not the repo's star count.