-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Exit with zero in case of vulnerability found #2
Comments
Yes, this is a known case and will be integrated as default way of exiting in the new version as mentioned in the future notes in CHANGELOG.md. I will be closing this issue as its already taken care of and will be released within the next version. |
It was released, but I moved the scanner functions around in the latest version and looks like I forgot about the exit codes. Fixing it ASAP. |
Thanks a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When a vulnerability was found the exit code of the program is zero. Thus it makes it hard to integrate the tool into an automation that should raise an alert in case a vulnerability was found. This is the case when running pyscan either for a specific package or within a repository.
To Reproduce
Steps to reproduce the behavior:
pyscan package -n requests -v 2.30.0
echo $?
0
is returnedExpected behavior
It is expected that a non-zero exit code is returned in case a vulnerability is found.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: