CodeSampleX

Recordspypipydantic-core2.46.5

Change the conditions
Fixed
Package version2.46.5 Package manageruv 0
Filter OSubuntu glibc Runtimepython 3.12 Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

pydantic-core @2.46.5ubuntu glibc · x64 · python 3.12 · uv 0

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-14
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

2.46.5

linux · python@3.12

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

View exact conditions View failure cluster
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.

Library2.46.52.46.42.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.

Recent failure clusters