Quickstart

• Type a package name or ID. Press Enter. Celebrate.
• Examples: Git.Git, firefox, tag: browser

Search syntax (copy-paste friendly)

• tag: web
• tags: git, vcs
• publisher: Microsoft
• id: Git.Git
• firefox tag: browser

How ranking works (short version)

• Package IDs are treated like VIPs.
• Prefix and fuzzy matching are on.
• Exact ID matches go first.

Troubleshooting

• No results? Try id: or publisher:.
• Unexpected ranking? Specify id: or tag:.

How pkgs.win search actually works (without the drama)

1) Search in one breath

We build a tiny JSON index at build time, ship it to your browser, and MiniSearch does the rest. No live API calls, just local speed.

2) Fields and ranking

• Indexed: name, ID, publisher, description, tags, moniker.
• Package ID gets a heavy boost. Exact ID matches float to the top.
• Prefix and fuzzy search help when your typing accuracy takes the day off.

3) Filter syntax

• tag: web / tags: web
• publisher: Microsoft
• id: Git.Git
• Combine: firefox tag: browser

4) Multiple filter values

• Commas and spaces work.
• Example: id: Git.Git, tags: git, vcs
• Multiple tags are ANDed; all must match.

5) Limitations (on purpose)

• Search shows the latest version only. That keeps the index fast and light.
• If a tag is missing, it is missing upstream in the manifests.

6) Data source

Everything comes from microsoft/winget-pkgs . We just make it easier to browse.