docs(worklist): the antivirus row reproduced from Defender's own history, and a row for the locally built exe #127
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!127
Loading…
Reference in a new issue
No description provided.
Delete branch "d4nkn3ss/Longshot:docs/worklist-antivirus-evidence"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Players keep getting Defender's "Trojan" warning on the Builder download, and the worklist row for it still waits on Hookshot's SignPath application, which doesn't carry over to Longshot. It now has evidence from Defender itself, and a second problem the row didn't cover: the game exe built on the player's PC gets flagged too.
What changed
docs/worklist.mdProgram:Win32/Contebrew.A!ml). S0 8 × 0.57 × 0.4, one PC.Flags and settings
None
Measurements
The evidence for the re-score: Defender's detection history (
Get-MpThreatDetection) on one Windows 11 PC, Nov 7-10, Hookshot files from GitHub; the table is in #46 (comment).main:
341d63a4(2026-11-12)this PR: docs/worklist-antivirus-evidence @
08748007Hardware: Windows 11, Defender engine 1.1.26100.4, signatures 1.463.271.0, cloud protection on
Scene: n/a (no game run)
Method: Defender's detection history read back (
Get-MpThreatDetection,Get-MpThreat); the setups' signatures (Get-AuthenticodeSignature) and version infoHow to reproduce: in PowerShell,
Get-MpThreatDetectionon a PC that downloaded a Hookshot release with Defender on341d63a408748007Testing
Tested: the score arithmetic and the table's order (highest first); no check reads
docs/worklist.md.Full suite:
python -I -B tests/run_all.pyon this branch @08748007, Windows 11: 498 passed, 3 failed, 35 skipped. The failures:tests/test_check_third_party.py(#80),tests/test_setup_runtime.py(#118) andtests/test_release.py(#119), all failing onmainthe same way.Not tested: whether a Longshot build is flagged the same way: there is no Longshot release yet. The local-exe row says so and stays at confidence 0.4.
Needs other testers: None
Screenshots
Nothing on screen
Risk and rollback
Docs only; reverting the commit is enough.
Issues
See #46
Checklist
For everyone
type(scope): description).main.python -I -B tests/run_all.pyrun and passing (any failure that also fails onmainis named above).third_party/untouched (a new folder with aPROVENANCE.mdinstead).If applicable
Assisted-by:/Co-Authored-By:trailers.🤖 Generated with Claude Code
Full game-free suite run on this branch (Windows 11); the results and the failures that also fail on main are now under Testing. Marking ready.
WIP: docs(worklist): the antivirus row reproduced from Defender's own history, and a row for the locally built exeto docs(worklist): the antivirus row reproduced from Defender's own history, and a row for the locally built exeView command line instructions
Checkout
From your project repository, check out a new branch and test the changes.