langchain-openai
pypi package · declared by 84 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 |
|---|---|---|
| langchain | 46 of 2,343 | 0.84 |
| langchain-community | 32 of 2,343 | 0.80 |
| langchain-core | 33 of 2,343 | 0.77 |
| langchain-anthropic | 16 of 2,343 | 0.73 |
| langgraph | 25 of 2,343 | 0.72 |
| langchain-google-genai | 16 of 2,343 | 0.70 |
| langchain-ollama | 10 of 2,343 | 0.63 |
| faiss-cpu | 8 of 2,343 | 0.53 |
| streamlit | 9 of 2,343 | 0.46 |
| sentence-transformers | 13 of 2,343 | 0.43 |
| python-dotenv | 34 of 2,343 | 0.40 |
| redis | 8 of 2,343 | 0.33 |
| pandas | 19 of 2,343 | 0.30 |
| uvicorn | 24 of 2,343 | 0.30 |
| openai | 22 of 2,343 | 0.29 |
| pydantic | 32 of 2,343 | 0.28 |
| fastapi | 23 of 2,343 | 0.27 |
| tiktoken | 10 of 2,343 | 0.26 |
| rich | 17 of 2,343 | 0.25 |
| scikit-learn | 8 of 2,343 | 0.22 |
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.