Skip to content

ci: attach SBOM (SPDX + CycloneDX) to every release - #28

Merged
opensource-SantanderAI merged 1 commit into
mainfrom
security/sbom-per-release
Jul 10, 2026
Merged

ci: attach SBOM (SPDX + CycloneDX) to every release#28
opensource-SantanderAI merged 1 commit into
mainfrom
security/sbom-per-release

Conversation

@opensource-SantanderAI

Copy link
Copy Markdown
Contributor

What

Adds a sbom.yml workflow that, on every published release, generates a Software Bill of Materials with syft (anchore/sbom-action, SHA-pinned) in SPDX JSON and CycloneDX JSON, and attaches both as release assets. workflow_dispatch runs upload them as workflow artifacts instead (verification path).

Why

Consumers can audit exactly what ships in each version. Complements GitHub's on-demand dependency-graph SBOM export (which reflects current main, not a given release).

Verification

Manual dispatch on main produces valid SPDX/CycloneDX documents as artifacts; the release path activates on the next published release.

New sbom.yml workflow: on each published release it generates a Software
Bill of Materials with syft (anchore/sbom-action, SHA-pinned) in the two
standard formats and attaches them as release assets. Manual dispatch
uploads them as workflow artifacts for verification. Least-privilege:
top-level permissions none, contents: write only at job level.
@opensource-SantanderAI
opensource-SantanderAI requested review from a team as code owners July 10, 2026 08:28
@opensource-SantanderAI
opensource-SantanderAI merged commit eb0e653 into main Jul 10, 2026
11 checks passed
@opensource-SantanderAI
opensource-SantanderAI deleted the security/sbom-per-release branch July 10, 2026 08:31
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 10, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant