microsoft / microsoft/winget-cli

Allow custom source to bypass SmartScreen

Open
#3,111 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-GPO Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Description of the new feature / enhancement

SmartScreen is good, but unfortunately sometimes it can be annoying due to network and other problems. winget now skips SmartScreen for default sources, and we wish to apply the same magic to custom sources that are trusted by the user.

Proposed technical implementation details

Add a new Group Policy option and CLI flag that explicitly "trusts" a source, allowing it to skip SmartScreen checks.

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 by locating the existing SmartScreen handling and the entry points for source-related Group Policy settings and CLI options. Define how an explicitly trusted custom source affects SmartScreen checks, then verify that both configuration paths consistently implement the requested bypass without changing default-source behavior.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.