New vulnerability findings data model

[ChrisSchneider]

What this PR does / why we need it:

Basic compatibility with new data model

Further UI updates are part of open-component-model/open-delivery-gear#186

Which issue(s) this PR fixes:

Fixes open-component-model/open-delivery-gear#187

[coderabbitai]

Warning

Review limit reached

@ChrisSchneider, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 109 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 71521df9-85df-45ed-8b48-448b813b4bb1

📥 Commits

Reviewing files that changed from the base of the PR and between eb63c53 and a8e8ae2.

📒 Files selected for processing (1)

• src/rescoring.js

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b9835df3-58db-44da-a7f9-4fee3d4a2c40

📥 Commits

Reviewing files that changed from the base of the PR and between 59baf97 and eb63c53.

📒 Files selected for processing (3)

• src/ocm/iter.js
• src/ocm/model.js
• src/rescoring.js

---

📝 Walkthrough

Walkthrough

findLabel now supports label aliases. Known label mappings use arrays. Rescoring uses Risk Profile terminology, retains CVE categorisation lookup, and displays updated CVSS and fixed-version data.

Changes

Risk profile and vulnerability updates

Layer / File(s)	Summary
Label lookup and metadata support src/ocm/iter.js, src/ocm/model.js	findLabel accepts one or multiple label names. knownLabelNames uses supported label-name arrays and removes mainSource.
Risk profile label UI src/rescoring.js	The component and related text use Risk Profile terminology. The lookup still uses knownLabelNames.cveCategorisation.
Vulnerability detail rendering src/rescoring.js	Details prefer cvss_score, fall back to cvss_v3_score, and show fixed_version when present.

Estimated code review effort: 2 (Simple) | ~10 minutes

Mergeability Score: ⚪ Minimal · up to eb63c

The PR is merge-ready after normal checks and review; no actionable merge-blocking risk remains.

Poem

I’m a rabbit reviewing labels with care,
Risk profiles now bloom in the UI air.
CVSS scores hop to the preferred place,
Fixed versions appear when they have a trace.
Aliases join the label parade—
A tidy little change is made.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The changes only update UI compatibility and labels; they do not implement the backend model, utilities, API routes, or scanner selection required by #187.	Add or link the required backend implementation, utilities, API routes, and active-scanner handling, or link the PR to the correct UI issue.
Out of Scope Changes check	⚠️ Warning	The UI and label changes are not supported by the backend-focused scope of #187, while the description assigns further UI work to #186.	Move UI-only changes to issue #186 or document their required dependency on the backend integration in #187.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: compatibility with the new vulnerability findings data model.
Description check	✅ Passed	The description states the purpose and linked issue, but omits the special notes and release note sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches 💡 1

⚔️ Resolve merge conflicts 💡

• Resolve merge conflict in branch new-vln-findings-data-model

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[8R0WNI3]

Please remove the label related changes from this PR.

[ChrisSchneider]

Note: this is just to make sure that nothing breaks. For broader UI updates there is a separate issue: open-component-model/open-delivery-gear#186

[zkdev]

Why do we use cvss_v3_score over cvss_score?

[ChrisSchneider]

It should be the other way round? https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Nullish_coalescing

So also when cvss_score is 0, cvss_score would be returned