SBOM on GitHub releases for the CRA: what to attach
As of 6 October 2026, the Cyber Resilience Act (Regulation (EU) 2024/2847) requires a manufacturer to draw up an SBOM for its product in a commonly used, machine-readable format covering at least the top-level dependencies (Annex I, Part II, point 1), and to keep it in the technical documentation (Annex VII). The text does not say that the SBOM must be public or attached to a GitHub release; attaching one is a convenient way to keep a per-release record. The main obligations apply from 11 December 2027.
What the Regulation says, and what it leaves open
| Question | Answer | Source |
|---|---|---|
| Must an SBOM exist? | Yes, for a manufacturer of a product with digital elements | Annex I, Part II, point 1 |
| Which format? | "Commonly used and machine-readable"; no format is named | Annex I, Part II, point 1 |
| How deep? | At the very least the top-level dependencies | Annex I, Part II, point 1 |
| Where is it kept? | In the technical documentation | Annex VII, points 2(b) and 8 |
| Must it be published? | No article requires publication. It goes to a market surveillance authority on a reasoned request; if you choose to share it with users, Annex II asks you to say where it can be accessed | Article 13(22), Annex VII point 8, Annex II point 9 |
| Per release? | The wording does not say; one SBOM per released version is the practical way to keep it accurate | Not specified |
Why GitHub releases are a good place
- The SBOM is stored next to the exact artefact it describes, with the release date.
- Users and downstream manufacturers can fetch it. A downstream manufacturer who builds your component into a product has due-diligence duties for its components (Article 13(5)), and a ready SBOM helps them.
- It is easy to automate in the release workflow, so it never goes stale.
What to do
- Generate the SBOM from the build, not by hand, in CycloneDX or SPDX JSON.
- Name the file after the version, for example
my-app-1.4.0.cdx.json, and add it as a release asset in the same workflow that builds the release. - Cover at least the top-level dependencies; include versions and package URLs so the list can be matched to vulnerability databases.
- Decide on purpose whether the SBOM is public. If it is not, store it with your technical documentation and be ready to hand it over on request.
- Keep the SBOM for the whole support period (see the support period guide) and regenerate it when dependencies change.
- Test the file with the SBOM checker; it runs in your browser. For field-level targets see the NTIA vs BSI comparison.
The repository check shows whether your GitHub repository already exposes a dependency graph that can be exported.
Article references
- Annex I, Part II, point 1: identify and document components, including an SBOM.
- Annex VII, points 2(b) and 8: the SBOM as part of the technical documentation, supplied on a reasoned request.
- Annex II, point 9: where the SBOM can be accessed, if you decide to make it available to users.
- Article 13(24): the Commission may specify the SBOM format by implementing act.
- Article 13(5): due diligence when integrating components.
- Articles 69 and 71: application dates.
This is general information, not legal advice. It does not say that any product is compliant or certified; check the Regulation for your case.
Free tools
- Product classifier: Is your product in scope, and in which category?
- SBOM checker: Check a CycloneDX or SPDX file in your browser.
- security.txt and disclosure policy: The contact file and policy the Regulation expects.
- Repository check: what a GitHub repository already shows.
Information generated from your inputs, with article references to Regulation (EU) 2024/2847. It is not legal advice and does not replace your own assessment; check the references against the Official Journal.