Skip to content
New issue

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 Only Scans "setup.py" For Code Execution #312

Open
cedricvanrompay-datadog opened this issue Mar 5, 2024 · 0 comments
Open

GuardDog Only Scans "setup.py" For Code Execution #312

cedricvanrompay-datadog opened this issue Mar 5, 2024 · 0 comments
Labels
enhancement New feature or request false-negative

Comments

@cedricvanrompay-datadog
Copy link
Member

# Only searches in setup.py to reduce false positives!

paths:
include:
- "*/setup.py"
- "*/code-execution.py"

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request false-negative
Projects
None yet
Development

No branches or pull requests

2 participants