It’s definitely reasonable to be concerned, but I think it’s a false positive. The released installer is uploaded straight from the artifact output by this build pipeline, run in GNOME CI using mingw upstream, so unless one of those two has issues I don’t see how this could be a real problem.
Just a quick remark, it might be irrelevant, but..
Windows Defender is usually extra sensitive if, somewhere in there, there an unsigned .exe or .dll, etc.
You might be thinking that everything is already signed. Of course we sign our binaries, how could you think we’re not doing that? Preposterous! But someone should go check. I’ve already removed the application, since I didn’t really use it (I use alternatives). So it’s hard for me to check this.