Skip to content

Wave-42: SBOM validate + pin cargo-cyclonedx (C04 L32) - #341

Merged
KooshaPari merged 2 commits into
mainfrom
feat/sl-w42-sbom-validate
Jul 20, 2026
Merged

Wave-42: SBOM validate + pin cargo-cyclonedx (C04 L32)#341
KooshaPari merged 2 commits into
mainfrom
feat/sl-w42-sbom-validate

Conversation

@KooshaPari

Copy link
Copy Markdown
Owner

Summary

  • Pin cargo-cyclonedx 0.5.9 in qgate + release workflows
  • Add sbom-policy SSOT, schema anchor validation script, security SelfCheck job
  • Wave-42 lane w42-sbom-validate

Test plan

  • pwsh ./scripts/sbom-validate-check.ps1 -SelfCheck
  • cargo test --test sbom_validate

Made with Cursor

Add sbom-policy SSOT, schema anchor validation, pinned cargo-cyclonedx 0.5.9
in qgate/release, blocking security SelfCheck, and tests/sbom_validate.rs.

Co-authored-by: Cursor <cursoragent@cursor.com>
@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: ASSERTIVE

Plan: Pro

Run ID: d13511d7-b4f5-4b0e-b3a8-4d15cc44223a

📥 Commits

Reviewing files that changed from the base of the PR and between 6923fb3 and 1281585.

📒 Files selected for processing (9)
  • .github/workflows/qgate.yml
  • .github/workflows/release.yml
  • .github/workflows/security.yml
  • CHANGELOG.md
  • SECURITY.md
  • docs/ops/fixtures/sbom-valid-minimal.cdx.json
  • docs/ops/sbom-policy.json
  • scripts/sbom-validate-check.ps1
  • tests/sbom_validate.rs
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/sl-w42-sbom-validate
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch feat/sl-w42-sbom-validate

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

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

@socket-security

socket-security Bot commented Jul 20, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedcargo/​serde@​1.0.03610090100100

View full report

Co-authored-by: Cursor <cursoragent@cursor.com>
@KooshaPari
KooshaPari merged commit 489f848 into main Jul 20, 2026
88 of 89 checks passed
@KooshaPari
KooshaPari deleted the feat/sl-w42-sbom-validate branch August 12, 2026 09:00
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