Skip to content

Latest commit

 

History

History
44 lines (31 loc) · 2.51 KB

PROVENANCE.md

File metadata and controls

44 lines (31 loc) · 2.51 KB

Verifying SDK build provenance with the SLSA framework

LaunchDarkly uses the SLSA framework (Supply-chain Levels for Software Artifacts) to help developers make their supply chain more secure by ensuring the authenticity and build integrity of our published SDK packages.

As part of SLSA requirements for level 3 compliance, LaunchDarkly publishes provenance about our SDK package builds using GitHub's generic SLSA3 provenance generator for distribution alongside our packages. These attestations are available for download from the GitHub release page for the release version under Assets > multiple.intoto.jsonl.

To verify SLSA provenance attestations, we recommend using slsa-verifier. Example usage for verifying SDK packages is included below:

# Set the version of the SDK to verify
SDK_VERSION=9.8.0
# Download package from PyPi
$ pip download --only-binary=:all: launchdarkly-server-sdk==${SDK_VERSION}

# Download provenance from Github release into same directory
$ curl --location -O \
  https://github.com/launchdarkly/python-server-sdk/releases/download/${SDK_VERSION}/multiple.intoto.jsonl

# Run slsa-verifier to verify provenance against package artifacts 
$ slsa-verifier verify-artifact \
--provenance-path multiple.intoto.jsonl \
--source-uri github.com/launchdarkly/python-server-sdk \
launchdarkly_server_sdk-${SDK_VERSION}-py3-none-any.whl

Below is a sample of expected output.

Verified signature against tlog entry index 76390194 at URL: https://rekor.sigstore.dev/api/v1/log/entries/24296fb24b8ad77ac42700bfad5eb5597ea8bda92acb470aade248c01ccfc44047c0cd5b4433021a
Verified build using builder "https://github.com/slsa-framework/slsa-github-generator/.github/workflows/generator_generic_slsa3.yml@refs/tags/v1.7.0" at commit c7b42a2e7486904978d77cf05a07280e7e1bbec2
Verifying artifact launchdarkly_server_sdk-9.2.2-py3-none-any.whl: PASSED

PASSED: Verified SLSA provenance

Alternatively, to verify the provenance manually, the SLSA framework specifies recommendations for verifying build artifacts in their documentation.

Note: These instructions do not apply when building our SDKs from source.