sqlalchemy
pypi package · declared by 108 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 |
|---|---|---|
| alembic | 32 of 2,343 | 0.76 |
| asyncpg | 17 of 2,343 | 0.65 |
| aiosqlite | 20 of 2,343 | 0.61 |
| greenlet | 10 of 2,343 | 0.58 |
| psycopg2-binary | 10 of 2,343 | 0.51 |
| pydantic-settings | 29 of 2,343 | 0.48 |
| bcrypt | 8 of 2,343 | 0.47 |
| fastapi | 46 of 2,343 | 0.45 |
| structlog | 9 of 2,343 | 0.45 |
| pyjwt | 14 of 2,343 | 0.44 |
| cryptography | 17 of 2,343 | 0.44 |
| redis | 13 of 2,343 | 0.43 |
| uvicorn | 34 of 2,343 | 0.37 |
| python-multipart | 18 of 2,343 | 0.36 |
| httpx | 31 of 2,343 | 0.34 |
| pydantic | 42 of 2,343 | 0.33 |
| typing-extensions | 12 of 2,343 | 0.31 |
| aiohttp | 13 of 2,343 | 0.30 |
| jinja2 | 13 of 2,343 | 0.29 |
| python-dotenv | 23 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.