Skip to content

Add build provenance / artifact attestations (SLSA) #33

Description

@piers-sinclair

Problem

There is no verifiable provenance linking the published zips and .nupkg to the source commit and workflow that built them. A SHA in the Homebrew/winget manifests proves the download matches what was published, but not that the published artifact came from this pipeline.

Fix

  • Add actions/attest-build-provenance to release.yml to generate SLSA build provenance for the release artifacts (and the NuGet package).
  • Document verification with gh attestation verify.

Priority: Medium

Metadata

Metadata

Assignees

No one assigned

    Labels

    securitySecurity hardening

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions