The heuristics powering this, as well as the Windows Defender whitelisting, are terrible.
My understanding is that a specific binary needs to become popular for it to stop being flagged. This creates a chicken and egg problem. Users are not incentivized to use the program with the warning. But removing the warning requires many people to ignore the warning.
This is a big problem for anyone writing Windows software. An indie developer or small open source project is not going to do well with this.
Conveniently M$ lets you buy a signing certificate to fix this.
https://stackoverflow.com/questions/48946680/how-to-avoid-th...
>My understanding is that a specific binary needs to become popular for it to stop being flagged. This creates a chicken and egg problem.
Given the recent npm axios compromise this sounds like a pretty smart move?