microsoft / microsoft/winget-cli
Remote Access tools (PUA)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Relevant area(s)
WinGet CLI
Description of the new feature / enhancement
The WinGet Community Repository has a policy for blocking PUA (Potentially Unsafe Applications).
I'd like to find a reasonable way to address the use of legitimate applications flagged as PUA rather than just an explicit block. This may require additional security reviews, administrative permissions for WinGet users to accept the risk or other mechanisms behaviors.
This work item is intended to track any applicable work necessary in the WinGet client to be able to allow these kinds of applications to be installed under certain circumstances.
Additional work would likely be required to adjust the policies for the community repository. If any other work items are created related to this, they should be linked to this issue.
Related to:
Proposed technical implementation details
No response
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 the WinGet CLI behavior and the related winget-pkgs pull request #345601. Determine the security, permission, and risk-acceptance requirements for allowing legitimate applications flagged as PUA. Done means a documented client-side approach exists for permitting these installations under defined circumstances, with any related policy work linked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100