Skip to content

fix(legacy): set * when given a range start with no provided upper bound - #163

Merged
westonsteimel merged 1 commit into
anchore:mainfrom
westonsteimel:legacy-rendering
Sep 10, 2026
Merged

westonsteimel merged 1 commit into
anchore:mainfrom
westonsteimel:legacy-rendering

Conversation

@westonsteimel

Copy link
Copy Markdown
Contributor

When converting to legacy Anchore CVE5 enriched data format based off of the upstream CVE5 format, set the upper bound as * when there is a greater_than_or_equal supplied in the spec file without a corresponding less_than or less_than_or_equal. This is because we need to distinguish between an equals and a range with no upper bound.

When converting to legacy Anchore CVE5 enriched data format based off of
the upstream CVE5 format, set the upper bound as `*` when there is a
`greater_than_or_equal` supplied in the spec file without a
corresponding `less_than` or `less_than_or_equal`.  This is because we
need to distinguish between an equals and a range with no upper bound.

Signed-off-by: Weston Steimel <author@code.w.steimel.me.uk>
@westonsteimel
westonsteimel merged commit e363ec3 into anchore:main Sep 10, 2026
2 checks passed
@westonsteimel
westonsteimel deleted the legacy-rendering branch September 10, 2026 14:44
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.

1 participant