pytorch - 💡(How to fix) Fix PyTorch CPU wheel index does not expose upload date metadata [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#178980Fetched 2026-04-08 02:22:02
View on GitHub
Comments
3
Participants
3
Timeline
26
Reactions
3
Assignees
Timeline (top)
labeled ×8mentioned ×5subscribed ×5commented ×3
RAW_BUFFERClick to expand / collapse

The PyTorch CPU wheel index does not expose upload date metadata for packages.

Many organizations are introducing supply-chain safety policies where dependency upgrades exclude packages uploaded within a recent grace window (e.g., last 2 weeks). This helps reduce the risk of consuming newly published poisoned packages.

Since the PyTorch CPU wheel index does not provide upload timestamps, tooling cannot apply this policy and users are forced to exempt the PyTorch CPU index from these protections.

It would be helpful if the index exposed package upload timestamps (or equivalent metadata) so dependency tooling can enforce time-based safety checks consistently.

For more context, see issue in uv - https://github.com/astral-sh/uv/issues/16846

cc @seemethere @malfet @atalman @tinglvv @nWEIdia

extent analysis

TL;DR

Exposing package upload timestamps in the PyTorch CPU wheel index would allow dependency tooling to enforce time-based safety checks.

Guidance

  • The lack of upload date metadata in the PyTorch CPU wheel index prevents the application of supply-chain safety policies that exclude recently uploaded packages.
  • To mitigate this, the index should be updated to include upload timestamps or equivalent metadata for packages.
  • Dependency tooling can then be configured to use this metadata to enforce time-based safety checks, such as excluding packages uploaded within a recent grace window.
  • Until this metadata is available, users may need to continue exempting the PyTorch CPU index from these protections, potentially increasing their risk exposure.

Notes

The implementation details of exposing upload timestamps in the PyTorch CPU wheel index are not specified in the issue, and would require further investigation.

Recommendation

Apply workaround: exempt the PyTorch CPU index from time-based safety checks until the index is updated to include upload timestamps, as this allows for some level of protection while awaiting the necessary metadata.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING