Yes please help us get it unblacklisted with your scanner. Security vendors work by keeping an eye out for the strange and unusual, and I myself am strange and unusual. The last month or so has been particularly bad with the virus scanners. Possibly due to some random change I made to the APE assembly or performance optimization in the C library. For example, we've needed to make changes in the past where error messages containing the word "oldskool" needed to be removed because virus scanners thought that made it a virus. Also if you get a chance, please upvote the redbean binaries on VirusTotal. I always try to do that (I'm "howishexeasier") since it helps people verify that a binary came from me.
Traditionally the open source community worked around these issues by not distributing binaries and instead asking people to build the software on their own. I like the convenience of binaries because open source software is becoming increasingly fragmented and impossible to build. So then people use interpreters instead of compilers, which are slower. In any case, I don't think the source code workaround is going to last forever. Many companies are now focusing on applying the virus scanner model to source code too.
Microsoft Defender can be particularly difficult about unsigned executables, which I appreciate is annoying for cross platform developers that don't have that problem elsewhere.
I've submitted this as a false positive under our enterprise licensing.
Traditionally the open source community worked around these issues by not distributing binaries and instead asking people to build the software on their own. I like the convenience of binaries because open source software is becoming increasingly fragmented and impossible to build. So then people use interpreters instead of compilers, which are slower. In any case, I don't think the source code workaround is going to last forever. Many companies are now focusing on applying the virus scanner model to source code too.