Request: signed checksum and keyring provenance for Python 3.13.5 embeddable package

[neyasiikea]

We are preparing a reproducible offline Windows runtime package and need artifact-bound provenance for the official Python embeddable package.

Target release:

• tag: v3.13.5
• artifact: python-3.13.5-embed-amd64.zip

Could the project publish or document the following for this exact artifact?

1. A signed SHA-256 checksum subject that explicitly covers the ZIP.
2. A detached signature for that checksum subject or the ZIP.
3. An independently verifiable official Python release keyring URL.
4. The signer fingerprint and exact signature coverage.
5. Artifact-bound LICENSE/NOTICE/third-party evidence.
6. A complete embedded Python/Hermes dependency and wheel URL/hash closure.

The release metadata JSON and a key ID alone are not sufficient to establish signed checksum coverage or official keyring provenance.

Please publish the material as official release assets or official Python release documentation if possible.

[hugovk]

Python 3.13.5 was released before we started adding SHA-256 checksums. However, you can find a MD5 checksum, Sigstore, SBOM and GPG files at https://www.python.org/downloads/release/python-3135/

We started adding SHA-256 instead of MD5 from 3.13.12 onwards, which you can find on pages like https://www.python.org/downloads/release/python-31312/ and also in in the Sigstore signatures.

We recommend using Sigstore to verify release artifacts, you can find more info about verification at https://www.python.org/downloads/metadata/sigstore/

The SBOM contains licence info.

Note that PGP signatures are no longer available from 3.14 onwards, see https://peps.python.org/pep-0761/

[neyasiikea]

Thank you, this is helpful.We will evaluate the official Sigstore path for the exact Python 3.13.5
embeddable artifact instead of treating the release-page MD5 or metadata JSON
as a signed SHA-256 checksum subject.
For an auditable verification record, could you please confirm:

1. The exact Sigstore bundle or .sigstore URL for:python-3.13.5-embed-amd64.zip
2. The expected certificate identity and OIDC issuer for the Python 3.13.5release artifact.
3. Whether the Sigstore bundle binds directly to the artifact digest, and whether the transparency-log inclusion proof is included or independently resolvable.
4. The exact SBOM URL for this release and whether the SBOM digest is bound to the same release artifact.
5. The official verification command or documented verification procedure for this exact artifact.

We will continue to require artifact-bound LICENSE/NOTICE evidence and acomplete Python/Hermes dependency URL/hash closure. We will not treat MD5,source commit signatures, or an unbound SBOM as artifact provenance.

[hugovk]

You can find the files linked at https://www.python.org/downloads/release/python-3135/ and additional files at https://www.python.org/ftp/python/3.13.5/

1. The exact Sigstore bundle or .sigstore URL for:python-3.13.5-embed-amd64.zip

https://www.python.org/ftp/python/3.13.5/python-3.13.5-embed-amd64.zip.sigstore

2. The expected certificate identity and OIDC issuer for the Python 3.13.5release artifact.

You can find it on https://www.python.org/downloads/metadata/sigstore/

3. Whether the Sigstore bundle binds directly to the artifact digest, and whether the transparency-log inclusion proof is included or independently resolvable.

I believe it is directly bound. The .sigstore file contains inclusionProof.

4. The exact SBOM URL for this release and whether the SBOM digest is bound to the same release artifact.

https://www.python.org/ftp/python/3.13.5/python-3.13.5-embed-amd64.zip.spdx.json

5. The official verification command or documented verification procedure for this exact artifact.

You can find it on https://www.python.org/download/sigstore/

We will continue to require artifact-bound LICENSE/NOTICE evidence and acomplete Python/Hermes dependency URL/hash closure.

The LICENSE.txt file is in the zip. We don't provide anything for Hermes.

Please check the files yourself before asking more questions about them.

[neyasiikea]

Thank you for the Sigstore and LICENSE.txt details. We inspected the bundle and SPDX file locally.

The remaining Python-specific closure gap is the SBOM/license detail:

1. Could you confirm whether the SPDX package entries are the complete dependency closure for python-3.13.5-embed-amd64.zip?
2. For packages whose license is NOASSERTION, is there an official per-package license conclusion or a canonical license-file URL/hash mapping we should use?
3. Does the SPDX package checksum for CPython intentionally equal the Sigstore artifact digest, and is that relationship documented as the artifact binding?
4. Is there an official list of the license files bundled in LICENSE.txt or a release-specific third-party license manifest?

We understand that Python does not provide Hermes dependency material. We will handle Hermes closure separately and will not attribute it to CPython.