Skip to content

fix: resolve CycloneDX VEX affects refs to document components - #5958

Open
shashidhar-02 wants to merge 1 commit into
ossf:mainfrom
shashidhar-02:fix-5953-cyclonedx-vex-component-resolution
Open

shashidhar-02 wants to merge 1 commit into
ossf:mainfrom
shashidhar-02:fix-5953-cyclonedx-vex-component-resolution

Conversation

@shashidhar-02

Copy link
Copy Markdown
  • Build component lookup map for CycloneDX VEX documents
  • Fall back to resolving affects ref or BOM-Link fragment against components
  • Extract product, version, vendor, and PURL from referenced component

Fixes #5953

- Build component lookup map for CycloneDX VEX documents
- Fall back to resolving affects ref or BOM-Link fragment against components
- Extract product, version, vendor, and PURL from referenced component

Fixes ossf#5953

Signed-off-by: shaashidhar <s94094838@gmail.com>
@shashidhar-02
shashidhar-02 force-pushed the fix-5953-cyclonedx-vex-component-resolution branch from c79d516 to dde9249 Compare October 15, 2026 01:23

This branch has not been deployed

No deployments
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.

fix: [bug description] CycloneDX VEX triage derives the product from the affects ref string instead of resolving the referenced component

1 participant