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
{{ message }}
This repository has been archived by the owner on Sep 16, 2022. It is now read-only.
Is there a practical difference between scans performed via the blackduck-docker-inpector on images and synopsys-detect's binary scan parameter for docker images? Additionally is there any expected difference between scans with Blackduck Hub and Synopsis' dedicated binary scanner called Blackduck Binary Analysis (BDBA)?
The text was updated successfully, but these errors were encountered:
I recently came across the answer to the docker-inspector and synopsys-detect JAR's. Activity log on the scan with synopsys-detect points that docker-inspector gets called by it at runtime. So using one or the other for scanning container images should yield the same results.
Adding on top of this. After successfully calling synopsys-detect with --detect.tools="BINARY_SCAN", results that appeared in BDBA seem to also appear in Blackduck Hub.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is there a practical difference between scans performed via the
blackduck-docker-inpector
on images andsynopsys-detect
's binary scan parameter for docker images? Additionally is there any expected difference between scans with Blackduck Hub and Synopsis' dedicated binary scanner called Blackduck Binary Analysis (BDBA)?The text was updated successfully, but these errors were encountered: