-
Notifications
You must be signed in to change notification settings - Fork 143
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
Update converter to current 5.0 format #97
base: main
Are you sure you want to change the base?
Conversation
Noticed on testing that this will need updating to handle the flattened affected/changed version list from rc5 |
9e37319
to
19475fd
Compare
Attempt to handle the new affected field has been implemented in latest commit, please let me know if this was an adequate solution. |
…o update-converter
…o update-converter
…container under fieldname: x_v4
@GianSantos @iamamoose Is this change still needed, or will the CVE List be upgraded using the current upconverter next week? |
The 5.0 schema has undergone some changes, this branch addresses the outdated 4.0 to 5.0 converter, and adds the functionality of converting a single json file containing multiple records in this format:
{"cveRecords":[json 4.0 object 1, json 4.0 object 2, etc]}.
Users who want to use the converter can also import the 'CVE_Convert' function into their scripts.