You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding the flag to fail when certain severity issues are found, the npm job doesn't fail. An error is thrown, but the npm job exit code is still a success (0).
My set up is as follows in order to reproduce:
As a note, when I run the same command with the failOnCVSS parameter, it all runs cleanly. And the report that generates does show critical vulnerabilities that SHOULD be causing the execution to fail
The owasp-dependency-check fails with error 15 (you can see in console) but the echo $? returns 0.
I have node16 and java 8 but I can reproduce it with node18 and java17.
I suppose that the problem (in current implementation) is in the "exec" command, it is asynchronous and it does not propagate the error
When adding the flag to fail when certain severity issues are found, the npm job doesn't fail. An error is thrown, but the npm job exit code is still a success (
0
).My set up is as follows in order to reproduce:
package.json
When I run the below command, the get the following:
npm run owasp
And when I check the exit code with
echo $?
, I get:The text was updated successfully, but these errors were encountered: