CodeSampleX

Recordspypipydantic-core2.46.4pydantic_core.SchemaSerializer

Change the conditions
Fixed
OSalpine musl Symbolpydantic_core.SchemaSerializer Architecturex64
Filter Runtimepython 3.12 Package version2.46.4 Package managerpip Execution contextpython libcmusl Clear filters

Current conditions

pydantic_core.SchemaSerializer @2.46.4alpine 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-27

Dependencies

LibraryVersionMeasured thereProjects
typing-extensions 4.16.0 contract passed 5 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.

Library2.46.52.46.4
typing-extensions 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.