-
Notifications
You must be signed in to change notification settings - Fork 60
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
Docker scan - map vulnerabilities to Dockerfile commands #975
Conversation
…factor_print_table
…factor_print_table
…prove_docker_scan
…factor_print_table
}() | ||
// Preform Binary scan | ||
extendedScanResults, cleanup, scanErrors, err := scanCmd.binaryScan() | ||
defer cleanup() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cleanup can be nil?
if len(rows[i].FixedVersions) != len(rows[j].FixedVersions) { | ||
return len(rows[i].FixedVersions) > len(rows[j].FixedVersions) | ||
} | ||
return rows[i].ImpactedDependencyName > rows[j].ImpactedDependencyName |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sverdlov93 this will effect the audit as well
added sort by package name after fixed version suggestion
@sverdlov93 notice now the sort will show same packages near each other, maybe we should add other sort inside package names by so it will look better. |
Enrich
jf docker scan
results with the origin command to the vulnerability found. And customize the docker scan table with more suitable parameters.Before:
After:
Depends on: jfrog/jfrog-client-go#817