Repository navigation
chore(security): state where torch reaches the lock in its audit exceptions - #124
Merged
Merged
Conversation
…ptions The reasons for PYSEC-2025-194 and PYSEC-2026-139 named only the benchmark extra; torch also comes in through the data extra, by torchcrepe for the audio pitch operator, and through every all extra. They stay open: the Linux wheels of each minor release from 2.11.0 to 2.15.0 require CUDA 13, and PYSEC-2026-139 has no fixed release. datarax calls no torch.jit and loads torchcrepe's weights with weights_only=True.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The same text for PYSEC-2026-139. Only the recorded reasons change; the ignores stay.
Evidence
uv.lock: torch 2.10.0 is required bydatarax[all],[all-cpu],[all-macos],[benchmark]and[data], and by litdata, mosaicml-streaming, torchaudio, torchcrepe andtorchvision. The old reason named only
benchmark.2.15.0 require
cuda-toolkit13 andnvidia-cudnn-cu13(wheel metadata on PyPI); 2.10.0requires
nvidia-cuda-runtime-cu12. PYSEC-2025-194 is fixed only from 2.13.0.torch.jit.script.Neither datarax's
srcnor torchcrepe callstorch.jit. datarax's one torch call istorch.load(..., weights_only=True)of torchcrepe's bundled weights (crepe_model.py:301).audit_lock.pyatf05e0e5, pip-audit 2.10.1) passes over all 15 extras;contract and hygiene tests: 87 passed; pre-commit passed.
Merge Danger
Door: two-way
Blast Radius: none
Text of two ignore reasons and a CHANGELOG entry; the audited set is unchanged.