CodeSampleX

Recordspypipydantic2.13.4fastapi.Path

Change the conditions
Fixed
Symbolfastapi.Path
Filter OSalpine musl Runtimepython 3.12 Package version2.13.4 Architecturex64 Package managerpip Execution contextpython libcmusl Clear filters

Current conditions

fastapi.Path @2.13.4alpine musl · x64 · python 3.12 · pip · python

2 of 2 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
2 / 2
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-08-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 4

First observed break

2.13.4

windows · python@3.10

3 FAIL · stage: UNKNOWN · fingerprint: sha256:ffbb4ffd3771cf576c11abebc6c7c29b590e9fb58cc223942da52c756caf54fe

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