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

Expose public CVE4 cves #108

Merged
merged 1 commit into from
Sep 6, 2023
Merged

Conversation

raboof
Copy link
Member

@raboof raboof commented Jul 18, 2023

As well as the cve5 ones

As well as the cve5 ones
Copy link
Member

@iamamoose iamamoose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The v4 and v5 schemas are different so is mixing them into a single json confusing?

@raboof
Copy link
Member Author

raboof commented Jul 21, 2023

The v4 and v5 schemas are different so is mixing them into a single json confusing?

Somewhat - the request that returns the list only produces a few fields that are mostly shared between the formats, so that might be OK.

When fetching the full individual CVEs, indeed the client will have to decide by the body how to parse it, and the dataVersion allows that.

@raboof raboof merged commit f1e1fed into apache:main Sep 6, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants