Flagged by Windows Defender since v1.14.20
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9.2k
- Forks
- 1.2k
- Avg merge
- 19m
- Merged PRs (30d)
- 4
Description
Hi,
I got a problem since I upgraded all my dependencies, my build was removed by Windows Defender (in a company).
So I rollback all dependency and I upgrade them one by one.
So, I can tell you that when I upgrade from 1.14.17 -> 1.14.22, I got flag. So I checked every version until I found the version 1.14.20 is problematic.
Of course I checked the code of that release and didn't see anything wrong, it's probably the upgrade of sqlite from 3.44 -> 3.45 that introduced a false positive.
So, I'm not sure if you're able to do anything about that. But maybe you can already confirm me that's really a false positive.
Let see if I'm the only one affected by that.
Thank you!
Here is the full message I got by Windows Defender:
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The report names no repository file or test; begin by comparing the 1.14.17–1.14.22 release artifacts and the SQLite 3.44–3.45 upgrade, then reproduce the Windows Defender detection. Done means confirming whether the 1.14.20 artifact is a false positive and documenting a verified finding or actionable cause.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- build-system, databases, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100