philips-software / philips-software/amp-devcontainer
Attest the SBOM
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 135
- Forks
- 8
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 28
Description
Current situation
SBOM is generated but not attested
Required situation
SBOM is generated and attested
Acceptance criteria
- SBOM attestation is in-place
- SBOM attestation is tested
- Attestation clean-up is extended/implemented for SBOM attestations
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the GitHub Actions workflow that generates the SBOM and review the linked GitHub artifact-attestation guidance first. Implement and test SBOM attestation, then inspect the existing attestation cleanup to extend it for SBOM attestations. Done means the SBOM is attested, the attestation is tested, and cleanup handles it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100