Skip to content

feat(policies): add fixed_version field to vulnerability finding schema#2994

Merged
migmartri merged 1 commit intochainloop-dev:mainfrom
migmartri:feat/vuln-finding-fixed-version
Apr 7, 2026
Merged

feat(policies): add fixed_version field to vulnerability finding schema#2994
migmartri merged 1 commit intochainloop-dev:mainfrom
migmartri:feat/vuln-finding-fixed-version

Conversation

@migmartri
Copy link
Copy Markdown
Member

Summary

  • Add optional fixed_version string field to PolicyVulnerabilityFinding proto message, allowing policies to report which version fixes a given vulnerability
  • The field follows the same pattern as other optional fields (recommendation, cvss_v3_score) — set via object.union in Rego policies, no builtin signature change needed

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 7 files

@migmartri migmartri requested a review from a team April 7, 2026 21:59
Add an optional fixed_version string field to PolicyVulnerabilityFinding,
allowing policies to report which version fixes a given vulnerability.
The field is optional and can be set via object.union in Rego policies,
consistent with other optional fields like recommendation and cvss_v3_score.

Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
@migmartri migmartri force-pushed the feat/vuln-finding-fixed-version branch from 3bc69e0 to 129da00 Compare April 7, 2026 22:00
@migmartri migmartri merged commit 0029aec into chainloop-dev:main Apr 7, 2026
14 checks passed
@migmartri migmartri deleted the feat/vuln-finding-fixed-version branch April 7, 2026 22:12
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.

2 participants