We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the title says, in the end I just allowed the executable on my system.
I suppose these updates are responsible for the specified behaviour since I haven't used Nim yet as of 2024.
The text was updated successfully, but these errors were encountered:
There's unfortunately no way for us to fix this issue, but you might be able to help by reporting false positives to your antivirus provider.
We will have to do that until all antiviruses learn not to block Nim executable (fx. choosenim) which might take a while.
I can't report every false positive unfortunately since some companies insist on only taking requests from customers.
Apologies for the bug.
Sorry, something went wrong.
Defender also thought 2.0.2 contains a virus Trojan:Win32/Vigorf.A 😅🙄
Trojan:Win32/Vigorf.A
No branches or pull requests
At the title says, in the end I just allowed the executable on my system.
I suppose these updates are responsible for the specified behaviour since I haven't used Nim yet as of 2024.
The text was updated successfully, but these errors were encountered: