Add SBOM generation workflow - #135
Merged
Merged
Conversation
Generates a production-only CycloneDX SBOM with trivy on every push to master and uploads it as a build artifact, so downstream vulnerability scanning can fetch it without cloning the repo. Same pattern as HealthSamurai/aidbox-ts-sdk#170. The aidbox-ts-sdk submodule is left uninitialized (no `submodules: recursive` on checkout) so this SBOM stays scoped to aidbox-ui's own pnpm-lock.yaml -- aidbox-ts-sdk is scanned by its own repo's SBOM workflow.
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
1 participant
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.
Summary
trivy fs --format cyclonedx) on every push tomastersbom) viaactions/upload-artifact, fetchable via the GitHub Actions API without cloning the reposubmodules: recursive, so theaidbox-ts-sdksubmodule stays an empty placeholder here and this SBOM only covers aidbox-ui's ownpnpm-lock.yaml-- aidbox-ts-sdk gets its own SBOM from its own repo's workflowSame pattern as HealthSamurai/aidbox-ts-sdk#170, which feeds a downstream vulnerability-scanning pipeline in
HealthSamurai/aidbox-vulnerabilities.Test plan
SBOMworkflow runs onmasterand uploads thesbomartifactgh api repos/HealthSamurai/aidbox-ui/actions/artifacts?name=sbomreturns it