beautifulsoup4
pypi package · declared by 102 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 |
|---|---|---|
| lxml | 17 of 2,343 | 0.59 |
| pymupdf | 9 of 2,343 | 0.42 |
| playwright | 12 of 2,343 | 0.41 |
| requests | 40 of 2,343 | 0.37 |
| httpx | 28 of 2,343 | 0.31 |
| aiofiles | 9 of 2,343 | 0.31 |
| tiktoken | 13 of 2,343 | 0.30 |
| pillow | 18 of 2,343 | 0.28 |
| aiohttp | 12 of 2,343 | 0.28 |
| openai | 23 of 2,343 | 0.27 |
| langchain | 9 of 2,343 | 0.27 |
| loguru | 9 of 2,343 | 0.27 |
| python-dotenv | 25 of 2,343 | 0.27 |
| numpy | 28 of 2,343 | 0.24 |
| jinja2 | 10 of 2,343 | 0.23 |
| sqlalchemy | 8 of 2,343 | 0.23 |
| pyyaml | 22 of 2,343 | 0.23 |
| pydantic | 28 of 2,343 | 0.21 |
| psutil | 8 of 2,343 | 0.21 |
| scikit-learn | 8 of 2,343 | 0.19 |
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.