Repository navigation
ci: publish verifiable security assessment evidence - #17
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The existing OSPS workflow keeps local Actions artifacts but does not publish verifiable results to GRC Store. Add the official reusable publisher with a pinned scanner and explicit coverage of OSPS Baseline 2026-08 maturity levels 1–3.
Pull requests run unsigned preflights; only the namespace-bound main branch publishes fresh results under CC0-1.0. The job uses a read-only repository token and scoped OIDC signing, with no long-lived or administrator credentials. Document that publication success is separate from baseline compliance and badge eligibility; existing scans and product behavior stay unchanged.
Validation: actionlint 1.7.12 passed for the caller workflow; official publisher/config contracts reviewed; PR preflight must pass before merge. No product version, normative ACC, production deployment, or branch-protection changes.