microsoft / microsoft/winget-cli
PowerShell feature parity: list --details
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Discussed in https://github.com/microsoft/winget-cli/discussions/6053
Originally posted by professionaltart February 14, 2026
Now that the winget list $package --details feature (https://github.com/microsoft/winget-cli/discussions/5759) is out of early testing and is live as of 1.28.190 (https://github.com/microsoft/winget-cli/discussions/6041), I wanted to check if a comparable option is in the pipeline for the PowerShell module?
I had a quick peek with Get-Module Microsoft.WinGet.Client | select * and saw nothing that seemed to match (apologies in advance if I missed it).
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 by reviewing discussions 6053, 5759, and 6041, then compare the live winget list $package --details behavior with the Microsoft.WinGet.Client PowerShell module exposed by Get-Module Microsoft.WinGet.Client | select *. Done means a comparable details option is available through the PowerShell module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100