CodeSampleX

Recordspypipydantic-settings2.14.2JsonConfigSettingsSource

Change the conditions
Fixed
SymbolJsonConfigSettingsSource
Filter OSalpine musl Runtimepython 3.12 Package version2.14.2 Architecturex64 Package managerpip Execution contextpython libcmusl Clear filters

Current conditions

JsonConfigSettingsSource @2.14.2alpine musl · x64 · python 3.12 · pip · python

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-20

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 6

First observed break

2.14.2

windows · python@3.10

4 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
pydantic 2.13.4 PASS All observations passed contract passed 8 project-days
pydantic 2.13.5 PASS All observations passed contract passed 1 project-day
python-dotenv 1.2.2 PASS All observations passed contract passed 7 project-days
python-dotenv 1.2.3 PASS All observations passed contract passed 1 project-day
typing-inspection 0.4.2 PASS All observations passed contract passed 7 project-days
typing-inspection 0.4.4 PASS All observations passed contract passed 1 project-day

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 0 · unchanged at every release: 3

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters