Request for guidance on using `reuse spdx` output with GitHub Attestations in spdx format

Open
#178 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
github

Research direction

Start by reviewing the actions/attest documentation and the referenced REUSE workflow, including reuse spdx, npm sbom, SPDX, and in-toto. A complete result would document whether and how these outputs can be attached to GitHub attestations, with an example workflow addressing all three questions.

Written by the indexing model from the issue text.

Description

Hi actions/attest team,

First, thank you for your excellent work on actions/attest! I’m new to supply chain security and am trying to understand how to incorporate SPDX SBOMs and licensing information into GitHub attestations using your GitHub Action. Most of my repositories are REUSE-compliant, and I’m trying to integrate the output of the reuse spdx command with attestations in GitHub.

If I’ve misunderstood anything, I apologize, and I’d greatly appreciate any guidance you can offer.

Questions:
  1. How can I integrate the SPDX SBOM and license data generated by the reuse spdx command into GitHub attestations using actions/attest?
  2. How can I generate and attach an SBOM using the npm sbom command and include it in a GitHub attestation using the in-toto format?
  3. Is there a recommended workflow or example for integrating REUSE-generated SPDX data with GitHub's attestation framework?

I’d appreciate any examples or advice on how to use your tool in this context to ensure SPDX compliance and proper licensing documentation.

Thank you again for your support!

Dominant language
TypeScript
Stars
187
Forks
65
Avg merge
3d 8h
Merged PRs (30d)
8

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/attest

All issues in actions/attest

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.