badges / badges/shields

Only WinGet Community Repository supported

Open
#11,402 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

service-badge
Dominant language
JavaScript
Stars
27.2k
Forks
5.6k
Avg merge
1d 8h
Merged PRs (30d)
46

Description

It seems that only the community repository is supported. The Microsoft Store (or custom repositories) are not supported.
https://github.com/badges/shields/blob/4daed4998f13a07d234a4eb8ed3996fb8516e461/services/winget/winget-version.service.js#L46

However, there are two types of repositories that can be added to WinGet: Microsoft.PreIndexed.Package and Microsoft.Rest:

  • The Microsoft.PreIndexed.Package compatible repository has a source.msix and source2.msix file that contains a SQLite file with all packages preindexed. This seems to be the default type when doing winget source add.
  • The Microsoft.Rest compatible repository hosts endpoints like /manifestSearch and /packageManifests/{id}. For example, https://storeedgefd.dsx.mp.microsoft.com/v9.0/packageManifests/9PM860492SZD gives the manifest information of Microsoft PC Manager on the Microsoft Store. The exact information I need (e.g. version of the package).

The msstore (Microsoft Store) repository seems to only support Microsoft.Rest. The winget (WinGet Community Repository) repository seems to only support Microsoft.PreIndexed.Package. Anyway, there is an official way to get the package information, instead of the unofficial way it is done now.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with services/winget/winget-version.service.js around line 46 and inspect how repository sources and package versions are currently obtained. Compare that flow with the Microsoft.Rest endpoints and repository types described in the issue; done means Microsoft Store and custom repositories can provide package information through the supported source behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.