Recordspypipydantic-core
Change the conditions
Current conditions
pydantic-core @2.46.5x64 · python 3.12 · pip · python
package-level total, not an API
0 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 failed
- Project observations
- nothing at this coordinate
- Contract verifications
- 0 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
ubuntu glibc · x64 · python 3.12 · pip
0 of 1 passed
Verified — this network ran a contract at this coordinate.
-
alpine musl · x64 · python 3.12 · pip · python
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
2.46.5
linux · python@3.12
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:6f01729cbd533929ff0a3c41fd99b21604634b4c6912871e5e4b216d5f438fa0
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| typing-extensions | 4.16.0 | PASS All observations passed | contract passed | 2 project-days |
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.46.5 | 2.46.4 | 2.20.1 |
|---|---|---|---|
| typing-extensions | 4.16.0 | 4.16.0 | 4.16.0 |
Moved: 0 · unchanged at every release: 1
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.