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
Tools declared alongside this one, ranked by association strength
Declared withRepositoriesvs chance
alembic25 of 2,3430.56
asyncpg15 of 2,3430.52
fastapi71 of 2,3430.50
pydantic88 of 2,3430.49
structlog14 of 2,3430.49
sqlalchemy29 of 2,3430.48
redis21 of 2,3430.48
httpx62 of 2,3430.48
uvicorn63 of 2,3430.48
bcrypt11 of 2,3430.47
prometheus-client11 of 2,3430.45
python-multipart33 of 2,3430.45
celery8 of 2,3430.45
pyjwt19 of 2,3430.44
aiosqlite14 of 2,3430.41
psycopg2-binary9 of 2,3430.40
apscheduler9 of 2,3430.39
psycopg8 of 2,3430.39
sqlmodel8 of 2,3430.38
typer26 of 2,3430.36

Every pair above is counted from the same evidence: repo manifest.

Used instead

candidates · shares a neighbourhood and refuses to co-occur

No 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.