torchvision
pypi package · declared by 79 of 2,343 sampled repositories · graph computed 2026-08-24
Counted from the runtime dependencies public repositories declare — not the resolved tree. A transitive dependency is a consequence; a declared one is a choice. Development dependencies are excluded because they repeat across every project in a language regardless of what is being built.
Declared with
ranked by association, not by count| Declared with | Repositories | vs chance |
|---|---|---|
| torch | 56 of 2,343 | 0.75 |
| einops | 27 of 2,343 | 0.69 |
| accelerate | 32 of 2,343 | 0.68 |
| diffusers | 15 of 2,343 | 0.66 |
| opencv-python | 22 of 2,343 | 0.66 |
| torchaudio | 15 of 2,343 | 0.64 |
| safetensors | 15 of 2,343 | 0.60 |
| timm | 10 of 2,343 | 0.59 |
| omegaconf | 10 of 2,343 | 0.57 |
| transformers | 34 of 2,343 | 0.55 |
| sentencepiece | 15 of 2,343 | 0.55 |
| peft | 14 of 2,343 | 0.54 |
| tokenizers | 12 of 2,343 | 0.54 |
| huggingface-hub | 22 of 2,343 | 0.52 |
| tensorboard | 9 of 2,343 | 0.52 |
| av | 8 of 2,343 | 0.51 |
| librosa | 9 of 2,343 | 0.49 |
| tqdm | 32 of 2,343 | 0.49 |
| datasets | 18 of 2,343 | 0.47 |
| wandb | 10 of 2,343 | 0.47 |
Every pair above is counted from the same evidence: repo manifest.
Used instead
candidates · shares a neighbourhood and refuses to co-occurNo alternative measured. A pair qualifies only if it shares a neighbourhood and then fails to appear together against an expectation that it would — and almost everything that shares a neighbourhood does appear together. That is the test working, not a gap in the data: similarity alone would list this tool’s closest neighbours as alternatives, and most of them are things it is used with.