You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
assurance: score and profile-validate the release SBOMs with declared thresholds, so the export grade cannot regress silently #507
The release-assurance framework (#398, #495) checks SBOM interoperability before a tag, but nothing scores the exported documents or validates them against a compliance profile. The grade has been flat at 60.3/D across five releases (v0.23.0 → v0.28.2) and nobody would have noticed a drop.
Proposal
Add a gate to the assurance catalog that, for the release's own CycloneDX and SPDX exports:
runs an independent validator (sbom-tools quality, sbom-tools validate --standard ntia,cisa-2026,cra, and sbomqs score for a second opinion) with the binary checksum-verified and version-pinned in the workflow;
publishes the numbers in the per-release report under docs/assurance/reports/ so the public record shows the trend.
Thresholds start at today's measured values (60.3 / 61.5 overall, 0 licences, 0 suppliers, 43.8 % similarity, standard COMPLIANT) and only move up when an export improvement lands — a ratchet, not a target.
Measured record and protocol: the competitive-study baseline (private planning repo, competitive-analysis/bomly-baseline.md). Planning: bomly-dev/bomly-planning#19 (H1.20) and #71.
Activity