jinja2
pypi package · declared by 133 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 |
|---|---|---|
| python-multipart | 25 of 2,343 | 0.41 |
| litellm | 16 of 2,343 | 0.39 |
| typer | 21 of 2,343 | 0.34 |
| rich | 32 of 2,343 | 0.33 |
| uvicorn | 37 of 2,343 | 0.33 |
| lxml | 8 of 2,343 | 0.33 |
| httpx | 34 of 2,343 | 0.31 |
| fastapi | 37 of 2,343 | 0.31 |
| pydantic | 48 of 2,343 | 0.31 |
| aiofiles | 11 of 2,343 | 0.31 |
| tenacity | 13 of 2,343 | 0.30 |
| pydantic-settings | 19 of 2,343 | 0.30 |
| sqlalchemy | 13 of 2,343 | 0.29 |
| mcp | 18 of 2,343 | 0.29 |
| starlette | 8 of 2,343 | 0.28 |
| networkx | 8 of 2,343 | 0.27 |
| websockets | 10 of 2,343 | 0.26 |
| pillow | 20 of 2,343 | 0.25 |
| psutil | 12 of 2,343 | 0.25 |
| tiktoken | 13 of 2,343 | 0.25 |
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.