alembic
pypi package · declared by 56 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 |
|---|---|---|
| asyncpg | 17 of 2,343 | 0.76 |
| sqlalchemy | 32 of 2,343 | 0.76 |
| greenlet | 9 of 2,343 | 0.65 |
| bcrypt | 9 of 2,343 | 0.61 |
| sqlmodel | 9 of 2,343 | 0.60 |
| psycopg2-binary | 9 of 2,343 | 0.59 |
| pydantic-settings | 25 of 2,343 | 0.56 |
| structlog | 9 of 2,343 | 0.56 |
| aiosqlite | 10 of 2,343 | 0.51 |
| redis | 11 of 2,343 | 0.49 |
| pyjwt | 11 of 2,343 | 0.48 |
| fastapi | 32 of 2,343 | 0.46 |
| python-multipart | 16 of 2,343 | 0.45 |
| uvicorn | 24 of 2,343 | 0.39 |
| cryptography | 9 of 2,343 | 0.38 |
| httpx | 18 of 2,343 | 0.31 |
| pydantic | 25 of 2,343 | 0.31 |
| pyyaml | 13 of 2,343 | 0.21 |
| python-dotenv | 12 of 2,343 | 0.20 |
| openai | 9 of 2,343 | 0.16 |
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.