ambolt

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

QuestionAnswerSource
Must an SBOM exist?Yes, for a manufacturer of a product with digital elementsAnnex I, Part II, point 1
Which format?"Commonly used and machine-readable"; no format is namedAnnex I, Part II, point 1
How deep?At the very least the top-level dependenciesAnnex I, Part II, point 1
Where is it kept?In the technical documentationAnnex 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 accessedArticle 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 accurateNot specified

Why GitHub releases are a good place

What to do

  1. Generate the SBOM from the build, not by hand, in CycloneDX or SPDX JSON.
  2. 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.
  3. Cover at least the top-level dependencies; include versions and package URLs so the list can be matched to vulnerability databases.
  4. 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.
  5. Keep the SBOM for the whole support period (see the support period guide) and regenerate it when dependencies change.
  6. 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

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

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.