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
guarddog/guarddog/analyzer/sourcecode/code-execution.yml
Line 1 in e49bf32
Lines 113 to 116 in e49bf32
This causes a lot of malicious packages not to be detected because they perform code execution in other files.
It's true that reporting every single code execution would result in a lot of noise though.
We should at least make this limitation clear, because a lot of people are surprised that GuardDog does not report some malicious packages. See:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
guarddog/guarddog/analyzer/sourcecode/code-execution.yml
Line 1 in e49bf32
guarddog/guarddog/analyzer/sourcecode/code-execution.yml
Lines 113 to 116 in e49bf32
This causes a lot of malicious packages not to be detected because they perform code execution in other files.
It's true that reporting every single code execution would result in a lot of noise though.
We should at least make this limitation clear, because a lot of people are surprised that GuardDog does not report some malicious packages. See:
The text was updated successfully, but these errors were encountered: