Skip to content
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

[pull] master from snyk:master #133

Merged
merged 9 commits into from
Jan 12, 2022
Merged

[pull] master from snyk:master #133

merged 9 commits into from
Jan 12, 2022

Conversation

pull[bot]
Copy link

@pull pull bot commented Jan 12, 2022

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

Yaron Schwimmer and others added 9 commits January 12, 2022 11:31
A previous change moved the filtering out of base image vulns (based on
the existance of `dockerfileInstruction`) to be before
`dockerfileInstruction` is assigned to the vulns, so all vulns were
filtered out in case we used the `exclude-base-image-vulns` option.

This fix moves the filtering back to where it was before, and
recalculates the value of `ok`, to account for the reason it was moved
in the first place.
Co-authored-by: @danlucian lucian.rosu@snyk.io

Allows users with snykUnmanagedVulnDB ff in org level to visualize
https://security.snyk.io/vuln/SNYK-UNMANAGED-CURL-2317584 rather than
nvd url

Depends on snyk/snyk-cpp-plugin#61

with feature flag
<img width="470" alt="Screen Shot 2022-01-11 at 11 53 47" src="https://user-images.githubusercontent.com/40601533/148922100-369c9d87-73c2-4dcc-881c-4dffac170758.png">

without feature flag
<img width="809" alt="Screen Shot 2022-01-11 at 11 53 03" src="https://user-images.githubusercontent.com/40601533/148922121-d03f6ac3-165c-4539-b8bc-f7ef5ce93ecb.png">
fix: exclude base image vulns filtering all vulns
feat: support unmanaged snyk security url
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants