ci(security): add OSV and Trivy scans with fork-safe SARIF; add SBOM … #1413
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.
What does this PR do?
Supply-chain security and workflow hardening, adding scanners, SBOMs, and signed release assets.
Changes (vs main):
.github/osv-scanner-config.yaml; initially non-blocking for triageanchore/sbom-action@v0) and upload artifact.sig/.crt) and a signedSHA256SUMSmanifestREADME.mdadds verification instructions and badges (CI, OpenSSF Scorecard, OSV/Trivy/DevSkim/SBOM);RELEASE_PROCEDURE.mdadds verification steps (checksums, Cosign, SBOM)Notes:
This is the updated version of PR #1309 with all conflicts resolved against the current main branch.
Standards checklist
CONTRIBUTING.mdFor new steps
--dry-runoption works with this step (N/A)--yesoption works with this step (N/A)