Measure Microsoft Defender's verdict on the release zip (CI, Windows runner)
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #277 by @thesprockee — merged
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 70/100
Research direction
Start by reading build.yml to reproduce the existing distribution build, then inspect the repository's workflow conventions. Create a manual workflow on a branch with a Linux build job and a windows-latest scan job using the specified Defender commands. Done means the workflow records Defender status, scan results, and threat detections without signing, secrets, or release wiring.
Written by the indexing model from the issue text.
Description
Before testers install the beta, measure what Microsoft Defender says about the release artifact on real Windows. VirusTotal reported 0/71 for a local build's BugSplat64.dll (sha256 78ef8638590a…); this is a baseline.
A manual workflow on a branch (not main, not wired into the release, nothing signed): a Linux job builds the dist zip exactly as build.yml does (no secrets, so no keys embedded) and a windows-latest job records Get-MpComputerStatus, runs MpCmdRun.exe -Scan -ScanType 3 -File <unzipped dir> -DisableRemediation (0 clean, 2 found) and prints Get-MpThreatDetection.
🤖 Generated with Claude Code
- Dominant language
- C++
- Stars
- 2
- Forks
- 3
- Avg merge
- 7h 54m
- Merged PRs (30d)
- 545
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from EchoTools/nevr-runtime
-
backlog
Difficulty 1/5 Under an hour Newbie friendliness 91/100
EchoTools/nevr-runtime#1108 ·
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#957 ·
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
EchoTools/nevr-runtime#796 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
EchoTools/nevr-runtime#781 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
EchoTools/nevr-runtime#771 ·
Maintainers usually reply within 1 day
All issues in EchoTools/nevr-runtime
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prestonbrown/helixscreen#1922 ·
Maintainers usually reply within 1 day
-
component: workspaces
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
zen-browser/desktop#16218 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Abort (SIGABRT) when stderr is a closed pipe: uncaught fmt::system_error in ccache_main's catchPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 3 days