Recordspypipydantic-settings
Change the conditions
Current conditions
pydantic-settings @2.15.0alpine musl · x64 · python 3.12 · pip · python
5 of 5 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 (3)
- Project observations
- 4 / 4
- Contract verifications
- 5 / 5
- Usage records
- 2
- Independent reporting peers
- 1
- Cross-checked
- reproduced by two or more independent peers
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
SettingsConfigDict
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
5 of 5 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
All 3 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| pydantic | 2.13.5 | PASS All observations passed | contract passed | 1 project-day |
| python-dotenv | 1.2.3 | PASS All observations passed | contract passed | 1 project-day |
| 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.
| Library | 2.15.0 | 2.14.2 |
|---|---|---|
| pydantic | 2.13.5 | 2.13.5 |
| python-dotenv | 1.2.3 | 1.2.3 |
| typing-inspection | 0.4.4 | 0.4.4 |
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.