Promote dev → main#13
Merged
Merged
Conversation
…idence The v0.2.17 release binaries have been independently scanned by VirusTotal. Every signature-based engine — including Microsoft's own — comes back clean. The Wacatac.C!ml flag on real Windows machines is from Defender's cloud-delivered ML classifier (the !ml suffix), which doesn't run on VirusTotal's static scans, hence the discrepancy. Both permanent VT URLs added to the false-positive section so users worried about the EXE can click through and see for themselves: - Portable: vti/file/27fa0046...d36f (0/64) - Installer: vti/file/de62ec18...36c3 (0/68) Also softened the closing line to reflect that SignPath Foundation signing is "in flight" rather than "on the roadmap" since the application is in. Docs-only; no widget behavior change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Auto-opened after dev tests passed on 2026-06-11T02:42:28Z.
Merge when you're ready. The release workflow does not trigger on this merge — it only runs when you tag a release on
main(e.g.npm version patch).