# Build provenance and component/notice evidence for one exact Torch CPU wheel

**URL:** <https://discuss.pytorch.org/t/build-provenance-and-component-notice-evidence-for-one-exact-torch-cpu-wheel/225950>\
**Category:** Uncategorized\
**Created:** [November 18, 2026, 2:33pm UTC](https://discuss.pytorch.org/t/build-provenance-and-component-notice-evidence-for-one-exact-torch-cpu-wheel/225950 "2026-11-18T14:33:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sampath\_Gaura](https://discuss.pytorch.org/user_avatar/discuss.pytorch.org/sampath_gaura/32/80368_2.png) [@Sampath\_Gaura](https://discuss.pytorch.org/u/Sampath_Gaura)\
**Post date:** [November 18, 2026, 2:33pm UTC](https://discuss.pytorch.org/t/build-provenance-and-component-notice-evidence-for-one-exact-torch-cpu-wheel/225950/1 "2026-11-18T14:33:53Z")

</div>

Could you point us to available publisher evidence for this exact distribution?

- Filename: torch-2.13.0+cpu-cp312-cp312-manylinux\_2\_28\_x86\_64.whl
- Publisher URL: [https://download-r2.pytorch.org/whl/cpu/torch-2.13.0%2Bcpu-cp312-cp312-manylinux\_2\_28\_x86\_64.whl](https://download-r2.pytorch.org/whl/cpu/torch-2.13.0%2Bcpu-cp312-cp312-manylinux_2_28_x86_64.whl)
- Length: 191817609 bytes
- SHA-256: 4ca4a9394b0c771238a4f73590fdbbc4debad85ed0fa63d026ae1b085da7d6e2

1. Build correspondence

Which source revision, submodules, applied patches, build recipe/job, toolchain, build environment and dependency materials produced this digest? Are immutable records linking those inputs and outputs available?

1. Attestations, build records and SBOM

Are publisher attestations, build records or an SBOM available? How does each record’s subject identify this exact wheel/digest, and what publisher identity and verification instructions accompany it?

1. Native inventory

Please identify compiled components, versions, origins, modifications and static/dynamic inclusion, including embedded dependencies and components elsewhere in the wheel.

The following immediate member names are limited directory declarations, not a complete component inventory:

- torch/lib/libaoti\_custom\_ops.so
- torch/lib/libbackend\_with\_compiler.so
- torch/lib/libc10.so
- torch/lib/libgomp.so.1
- torch/lib/libjitbackend\_test.so
- torch/lib/libshm.so
- torch/lib/libtorch.so
- torch/lib/libtorch\_cpu.so
- torch/lib/libtorch\_global\_deps.so
- torch/lib/libtorch\_python.so
- torch/lib/libtorchbind\_test.so

1. Licence/NOTICE mapping and delivery

Which licence/NOTICE materials apply to each included component, how are they mapped to this exact wheel, and where are required notices or accompanying materials delivered—for example, wheel entries, companion documentation or other supplied materials?

Please identify relevant modifications and the scope of any partial mapping. We seek component/delivery mappings rather than repetition of licence-text comparisons.

For recipe context, we reviewed this public source revision:

> **[GitHub - pytorch/pytorch at cf30153c4c131c8164ee7798e5022d810682e2cb](https://github.com/pytorch/pytorch/tree/cf30153c4c131c8164ee7798e5022d810682e2cb)**
>
> cf30153c4c131c8164ee7798e5022d810682e2cb

This is not an assertion that it built the wheel. Embedded version/git fields are self-reported claims; matching licence text and declared names do not identify all compiled components or prove build provenance.

Links to available immutable records, with coverage and limitations clearly stated, would be helpful.
