Skip to content

Document the evolving Windows SmartScreen errors#541

Merged
sdglitched merged 1 commit intomainfrom
sign
Apr 25, 2026
Merged

Document the evolving Windows SmartScreen errors#541
sdglitched merged 1 commit intomainfrom
sign

Conversation

@gridhead
Copy link
Copy Markdown
Owner

@gridhead gridhead commented Apr 24, 2026

Document the evolving Windows SmartScreen errors

Fixes #540

Summary by Sourcery

Documentation:

  • Add a README section explaining recurring Microsoft SmartScreen false positives for Windows binaries and guidance on bypassing the warnings.

@gridhead gridhead added this to the Luna VI milestone Apr 24, 2026
@gridhead gridhead requested a review from sdglitched April 24, 2026 04:28
@gridhead gridhead self-assigned this Apr 24, 2026
@gridhead gridhead added the documentation Improvements or additions to documentation label Apr 24, 2026
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai Bot commented Apr 24, 2026

Reviewer's Guide

Documents recurring Windows SmartScreen false positives for the Nuitka-built executables and explains how users can safely bypass these warnings and verify the build integrity.

Flow diagram for bypassing Windows SmartScreen warning

flowchart TD
  A[User launches Nuitka-built executable] --> B[Windows SmartScreen warning appears]
  B --> C{Does user trust the application?}
  C -->|No| D[User cancels execution]
  D --> E[Application does not run]
  C -->|Yes, after reading documentation| F[User clicks More Info]
  F --> G[User clicks Run anyway]
  G --> H[Executable runs successfully]
  H --> I[User can optionally verify integrity by building from source or reviewing CI builds]
Loading

File-Level Changes

Change Details Files
Add a warning section describing Windows SmartScreen false positives for Nuitka-built executables and how to proceed safely.
  • Introduce a new 'Warning' subsection under the releases section of the README.
  • Explain that a migration from PyInstaller to Nuitka correlates with increased Microsoft SmartScreen warnings due to lack of code signing.
  • Clarify that SmartScreen detections are false positives stemming from unsigned binaries, not from malicious code.
  • Provide step-by-step guidance for bypassing SmartScreen by using 'More Info' → 'Run anyway'.
  • Justify the absence of code signing based on project cost constraints, note that binaries are built transparently via GitHub Actions, and invite users to verify integrity by building locally.
README.md

Assessment against linked issues

Issue Objective Addressed Explanation
#540 Add documentation explaining the Windows SmartScreen warnings for Nuitka-built executables, including why they occur (lack of code signing), that they are false positives, how to bypass them (More Info → Run anyway), and reassurance about build transparency and local verification.

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue, and left some high level feedback:

  • The new SmartScreen section contains a small grammar issue in the sentence starting with “Not only are the executable binaries are transparently built…” – drop the second “are” and consider simplifying the sentence for clarity.
  • The wording around SmartScreen (e.g., “false positives,” “untruthful detections,” “frivolous warnings”) is somewhat loaded; consider rephrasing more neutrally and focusing on explaining the cause (no code signing) and mitigation steps to keep the tone professional and clear for security‑conscious users.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- The new SmartScreen section contains a small grammar issue in the sentence starting with “Not only are the executable binaries are transparently built…” – drop the second “are” and consider simplifying the sentence for clarity.
- The wording around SmartScreen (e.g., “false positives,” “untruthful detections,” “frivolous warnings”) is somewhat loaded; consider rephrasing more neutrally and focusing on explaining the cause (no code signing) and mitigation steps to keep the tone professional and clear for security‑conscious users.

## Individual Comments

### Comment 1
<location path="README.md" line_range="212-215" />
<code_context>
+and open source software, we cannot afford to make additional expenses to
+subscribe to various
+[code signing](https://en.wikipedia.org/wiki/Code_signing) services. Not only
+are the executable binaries are transparently built on
+[GitHub Actions](https://github.com/gridhead/gi-loadouts/actions), folks are
+invited to verify the project's integrity by compiling things locally.
</code_context>
<issue_to_address>
**issue (typo):** Duplicate "are" in this sentence makes it grammatically incorrect.

The phrase "are the executable binaries are transparently built" has an extra "are". For example, you could write "Not only are the executable binaries transparently built on" or "Not only are the executable binaries built transparently on".

```suggestion
[code signing](https://en.wikipedia.org/wiki/Code_signing) services. Not only
are the executable binaries transparently built on
[GitHub Actions](https://github.com/gridhead/gi-loadouts/actions), folks are
invited to verify the project's integrity by compiling things locally.
```
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread README.md
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a "Warning" section to the README to address Microsoft SmartScreen false positives caused by the transition to Nuitka and the absence of code signing. The review feedback suggests improving the professional tone by replacing "untruthful" with "inaccurate" and correcting a grammatical error involving a "not only... but also" structure and a repeated word.

Comment thread README.md Outdated
[Nuitka](https://nuitka.net/) for building application executable binaries,
we have noticed frequent
[Microsoft SmartScreen](https://en.wikipedia.org/wiki/Microsoft_SmartScreen)
errors. These are false positives and untruthful detections only because the
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The term 'untruthful' is generally used to describe human behavior. For software detections, 'inaccurate' or 'erroneous' is more appropriate and professional.

Suggested change
errors. These are false positives and untruthful detections only because the
errors. These are false positives and inaccurate detections only because the

Comment thread README.md
Comment on lines +212 to +215
[code signing](https://en.wikipedia.org/wiki/Code_signing) services. Not only
are the executable binaries are transparently built on
[GitHub Actions](https://github.com/gridhead/gi-loadouts/actions), folks are
invited to verify the project's integrity by compiling things locally.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This sentence contains a grammatical error (the word 'are' is repeated) and is missing the 'but also' conjunction required to complete the 'not only' correlative structure.

Suggested change
[code signing](https://en.wikipedia.org/wiki/Code_signing) services. Not only
are the executable binaries are transparently built on
[GitHub Actions](https://github.com/gridhead/gi-loadouts/actions), folks are
invited to verify the project's integrity by compiling things locally.
[code signing](https://en.wikipedia.org/wiki/Code_signing) services. Not only
are the executable binaries transparently built on
[GitHub Actions](https://github.com/gridhead/gi-loadouts/actions), but folks are
also invited to verify the project's integrity by compiling things locally.

@gridhead gridhead force-pushed the sign branch 2 times, most recently from d501245 to 3b0bbb7 Compare April 24, 2026 06:07
Signed-off-by: Akashdeep Dhar <akashdeep.dhar@gmail.com>
Copy link
Copy Markdown
Collaborator

@sdglitched sdglitched left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 🚀

@sdglitched sdglitched merged commit e504d5f into main Apr 25, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document the evolving Windows SmartScreen errors

2 participants