CodeSampleX

Recordspypipydantic2.13.5pydantic.BaseModel

Change the conditions
Fixed
Package version2.13.5 Symbolpydantic.BaseModel
Filter OSubuntu glibc Runtimepython 3.12 Architecturex64 Package managerpip libcglibc Clear filters

Current conditions

pydantic.BaseModel @2.13.5ubuntu glibc · x64 · python 3.12 · pip

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
Last recorded
2026-08-30

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 3

First observed break

2.13.5

linux · python@3.12

1 FAIL · stage: UNKNOWN · fingerprint: sha256:6f01729cbd533929ff0a3c41fd99b21604634b4c6912871e5e4b216d5f438fa0

Library Version Health Measured there Projects
pydantic-core 2.46.5 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
annotated-types 0.8.0 PASS All observations passed contract passed 2 project-days
typing-extensions 4.16.0 PASS All observations passed contract passed 2 project-days
typing-inspection 0.4.4 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.

Moved: 1 · 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