microsoft / microsoft/winget-pkgs
Feature request : reporting badly referenced/tagged programs
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11.1k
- Forks
- 9.7k
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 376
Description
Description of the new feature/enhancement
Right now, anybody can add new manifests to the repository. Even if everything is checked by robot for security, there is one thing that is not checked : tags validity.
This happened to me moments ago.
I tried to install mpv player (https://mpv.io/) by typing winget install mpv.
However, SMplayer (https://www.smplayer.info/) began to install instead of mpv.
C:\Users\theo.basty>winget install mpv
Found SMPlayer [SMPlayer.SMPlayer]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://wingetrepo.blob.core.windows.net/smplayer/smplayer-20.4.2-x64.exe
██████████████████████████████ 21.0 MB / 44.4 MB
Package download canceled.
I did a search to find out why SMPlayer was found even if it is completely diffenrent than mpv, and i found this :
C:\Users\theo.basty>winget search mpv
Name Id Version Matched
-------------------------------------------
SMPlayer SMPlayer.SMPlayer 20.4.2 Tag: mpv
When i checked the manifest file of SMPlayer, they indead tagged it as mpv. (commit b950fcfce8494a19f46b91070892368a419b61af).
It would be nice to have a way to report these manifests which confuse people. Maybe a new kind of issue on this repo ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SMPlayer manifest and commit b950fcfce8494a19f46b91070892368a419b61af referenced in the report, then review how the repository handles manifest validation and issue submissions. The issue does not name files, tests, or an entry point. Done would require an agreed way to report misleading tags and a defined check or workflow for preventing them.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100