-
Notifications
You must be signed in to change notification settings - Fork 549
feat(vex): integrate lib4vex for VEX document management #5124
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good.
Be careful using logger.info as this can become very noisey very quickly. Suggest that you change this to debug.
Hey! I've implemented the suggested changes and fixed the tests for Week 1 tasks. However, CI on my fork is acting up a bit (even after a re-run) ...waiting for the CI here. Let me know if there's any changes required. |
I've approved CI to run, and I've also submitted a ticket to get you added to the "cve-bin-tool-read" group so you shouldn't have to wait for me to trigger CI runs. You'll get an invite in the next day or so when our ops team gets time to send them out, please accept it! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, Some Vex and Vex Handler Tests are failing, I'll make another pass once they are fixed.
b879cbd
to
ee8efb1
Compare
e2bcf78
to
13f3f4a
Compare
Integrate lib4vex for VEX document handling
This PR introduces a centralized VexHandler class that leverages lib4vex for parsing, validation, generation, and conversion of VEX documents across multiple formats (CSAF, CycloneDX, and OpenVEX).
Changes
Testing
Unit tests cover:
It is a draft PR and the code still needs changes before merging it