-
Notifications
You must be signed in to change notification settings - Fork 1
feat: add trivy #164
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
base: main
Are you sure you want to change the base?
feat: add trivy #164
Conversation
…ivy vulnerability scanning
…e path in push image step
…workflows into feat/add-trivy
…workflows into feat/add-trivy
PR ready for review @puehringer @dvvanessastoiber @dvviktordelev |
@dv-hossam-radwan did a test run with this PR and visynKB in case you want to take a look: https://github.com/datavisyn/visyn_kb/actions/runs/15003505026 |
exit-code: '1' | ||
ignore-unfixed: false | ||
vuln-type: 'os,library' | ||
severity: 'MEDIUM,HIGH,CRITICAL' |
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.
I'm not sure if 57A7 we should treat medium ones...
severity: 'MEDIUM,HIGH,CRITICAL' | |
severity: 'HIGH,CRITICAL' |
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.
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.
Looks good to me code-wise 👍 let's also wait for approval by @puehringer and @dvviktordelev
No description provided.