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.

Sign up for GitHub

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

Jump to bottom

CPEs in JSON output should be a formatted string #268

Closed
wagoodman opened this issue Apr 1, 2021 · 0 comments · Fixed by #273
Closed

CPEs in JSON output should be a formatted string #268

wagoodman opened this issue Apr 1, 2021 · 0 comments · Fixed by #273
Labels
bug Something isn't working epic: grype / engine integration Replace vulnerability matching in policy engine with grype calls

Comments

@wagoodman
Copy link
Contributor

wagoodman commented Apr 1, 2021 •
edited
Loading

Today the CPEs in the JSON format are showing the individual WFN fields within an object for each CPE. These should be displayed in the CPE formatted string (e.g. cpe:2.3:a:vendor:product:*:*...).
@wagoodman wagoodman added bug Something isn't working epic: grype / engine integration Replace vulnerability matching in policy engine with grype calls labels Apr 1, 2021
@wagoodman wagoodman mentioned this issue Apr 1, 2021
Merged
@wagoodman wagoodman changed the title CPEs in JSON output should use the URI binding format CPEs in JSON output should be a formatted string Apr 1, 2021
@nightfurys nightfurys mentioned this issue Apr 21, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working epic: grype / engine integration Replace vulnerability matching in policy engine with grype calls
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Represent CPEs as formatted strings anchore/grype
1 participant
@wagoodman