nltk
pypi package · declared by 50 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 |
|---|---|---|
| transformers | 19 of 2,343 | 0.48 |
| datasets | 10 of 2,343 | 0.41 |
| sentence-transformers | 8 of 2,343 | 0.41 |
| langchain | 9 of 2,343 | 0.41 |
| scikit-learn | 11 of 2,343 | 0.41 |
| openai | 18 of 2,343 | 0.37 |
| scipy | 9 of 2,343 | 0.34 |
| tqdm | 10 of 2,343 | 0.27 |
| numpy | 16 of 2,343 | 0.26 |
| requests | 14 of 2,343 | 0.24 |
| torch | 8 of 2,343 | 0.24 |
| pandas | 8 of 2,343 | 0.21 |
| uvicorn | 10 of 2,343 | 0.20 |
| rich | 8 of 2,343 | 0.19 |
| fastapi | 10 of 2,343 | 0.19 |
| pyyaml | 9 of 2,343 | 0.17 |
| pydantic | 11 of 2,343 | 0.14 |
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.