pydantic-settings
pypi package · declared by 135 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 | 25 of 2,343 | 0.56 |
| asyncpg | 15 of 2,343 | 0.52 |
| fastapi | 71 of 2,343 | 0.50 |
| pydantic | 88 of 2,343 | 0.49 |
| structlog | 14 of 2,343 | 0.49 |
| sqlalchemy | 29 of 2,343 | 0.48 |
| redis | 21 of 2,343 | 0.48 |
| httpx | 62 of 2,343 | 0.48 |
| uvicorn | 63 of 2,343 | 0.48 |
| bcrypt | 11 of 2,343 | 0.47 |
| prometheus-client | 11 of 2,343 | 0.45 |
| python-multipart | 33 of 2,343 | 0.45 |
| celery | 8 of 2,343 | 0.45 |
| pyjwt | 19 of 2,343 | 0.44 |
| aiosqlite | 14 of 2,343 | 0.41 |
| psycopg2-binary | 9 of 2,343 | 0.40 |
| apscheduler | 9 of 2,343 | 0.39 |
| psycopg | 8 of 2,343 | 0.39 |
| sqlmodel | 8 of 2,343 | 0.38 |
| typer | 26 of 2,343 | 0.36 |
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.