Adding the Task in our CI pipelines (previously working on default settings), now results in various errors, starting with Binskim fails (see below):
BinSkim completed with exit code 1
##[error]Error running binskim job: 1 of 1
##[error]GuardianErrorExitCodeException: binskim completed with an Error exit code: 1. BinSkim failed. Verify the target(s) to be scanned. BinSkim targets must be a specific filename, or a pattern with a wildcard like *.dll, dir\*.dll, or dir\*
To be clear: we haven't changed anything, and this is NOT a failure due to some issue with the code being scanned. This appears to have been introduced by whatever changes have been made to the underlying Nuget package by Microsoft dev team, since it was working a week ago.
We're trying to use this in a non-production environment to find out if its a suitable product to use as our primary SAST/DAST tool. Atm we can't do anything with it.