-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improve VEX reports to handle Go's versioned entries without the v
prefix
#27
Comments
Trivy is working on fixing the |
PR which adds the initial duplicated entries to fix this - #28. |
Now Rancher's VEX Hub reports have the needed entry for Go dependencies and can properly remove false-positives with Trivy in both Repo scan with Rancher's VEX Hub
Image scan with Rancher's VEX Hub
|
@knqyf263 FYI ^ |
Awesome! |
While working on #23 (comment) (see the comments below the linked one) we, together with Trivy's team, identified that there are discrepancies (aquasecurity/trivy#7242) in the way that Trivy generates the affected version for Go's dependencies when scanning in image versus repo mode.
This happens, partially, because Go itself (golang/go#68152) doesn't properly follow the PURL spec (package-url/purl-spec#294) and adds the
v
prefix to the dependencies' versions.The plan is to have doubled VEX entries for Go packages containing both the
v
prefix and without it. This way we believe that we can be sure that any VEX scanner will correctly match our VEXed entries.The text was updated successfully, but these errors were encountered: