|
2 | 2 |
|
3 | 3 | LaunchDarkly uses the [SLSA framework](https://slsa.dev/spec/v1.0/about) (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. |
4 | 4 |
|
5 | | -As part of [SLSA requirements for level 3 compliance](https://slsa.dev/spec/v1.0/requirements), LaunchDarkly publishes provenance about our SDK package builds using [GitHub's generic SLSA3 provenance generator](https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/README.md#generation-of-slsa3-provenance-for-arbitrary-projects) for distribution alongside our packages. These attestations are available for download from the GitHub release page for the release version under Assets > `multiple-provenance.intoto.jsonl`. |
| 5 | +As part of [SLSA requirements for level 3 compliance](https://slsa.dev/spec/v1.0/requirements), LaunchDarkly publishes provenance about our SDK package builds using [GitHub's generic SLSA3 provenance generator](https://github.com/slsa-framework/slsa-github-generator/blob/main/internal/builders/generic/README.md#generation-of-slsa3-provenance-for-arbitrary-projects) 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`. |
6 | 6 |
|
7 | 7 | To verify SLSA provenance attestations, we recommend using [slsa-verifier](https://github.com/slsa-framework/slsa-verifier). Example usage for verifying SDK packages is included below: |
8 | 8 |
|
| 9 | +<!-- x-release-please-start-version --> |
9 | 10 | ``` |
10 | | -# Download packages from PyPi |
| 11 | +# Download package from PyPi |
11 | 12 | $ pip download --only-binary=:all: launchdarkly-server-sdk |
12 | 13 |
|
13 | | -# Download provenance from Github release |
| 14 | +# Download provenance from Github release into same directory |
14 | 15 | $ curl --location -O \ |
15 | | - https://github.com/launchdarkly/python-server-sdk/releases/download/VERSION/multiple.intoto.jsonl |
| 16 | + https://github.com/launchdarkly/python-server-sdk/releases/download/9.2.0/multiple.intoto.jsonl |
16 | 17 |
|
17 | 18 | # Run slsa-verifier to verify provenance against package artifacts |
18 | 19 | $ slsa-verifier verify-artifact \ |
19 | | ---provenance-path multiple-provenance.intoto.jsonl \ |
| 20 | +--provenance-path multiple.intoto.jsonl \ |
20 | 21 | --source-uri github.com/launchdarkly/python-server-sdk \ |
21 | | -launchdarkly_server_sdk-VERSION-py3-none-any.whl |
| 22 | +launchdarkly_server_sdk-9.2.0-py3-none-any.whl |
| 23 | +Verified signature against tlog entry index 71399397 at URL: https://rekor.sigstore.dev/api/v1/log/entries/24296fb24b8ad77a95c53f2cb33fe2e8c8fbc04591ebf26e4d2796fb2975c3ba377f1dc14507f421 |
| 24 | +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 5e818265c9f85ae9a111290bd6a4fad1a08786e9 |
| 25 | +Verifying artifact launchdarkly_server_sdk-9.2.0-py3-none-any.whl: PASSED |
| 26 | +
|
| 27 | +PASSED: Verified SLSA provenance |
22 | 28 | ``` |
| 29 | +<!-- x-release-please-end --> |
23 | 30 |
|
24 | 31 | Alternatively, to verify the provenance manually, the SLSA framework specifies [recommendations for verifying build artifacts](https://slsa.dev/spec/v1.0/verifying-artifacts) in their documentation. |
25 | 32 |
|
|
0 commit comments