CodeSampleX

Recordsnpm@jest/schemas29.6.3SnapshotFormat

Change the conditions
Fixed
SymbolSnapshotFormat Package managernpm
Filter OSalpine musl Runtimenode 22 Package version29.6.3 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

SnapshotFormat @29.6.3alpine musl · x64 · node 22 · npm · node

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 (3)

Project observations
nothing at this coordinate
Contract verifications
2 / 2
Last recorded
2026-08-27

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

29.6.3

linux · node@22.23 · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
@sinclair/typebox 0.27.12 CANDIDATE Correlated change; unproven combination contract passed 47 project-days
@sinclair/typebox 0.27.8 CANDIDATE Correlated change; unproven combination contract passed 1 project-day

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.

Library30.4.129.6.3
@sinclair/typebox 0.34.52 0.27.8

Moved: 1 · unchanged at every release: 0

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

Showing the 12 most-reported of 23 recorded failure clusters. The rest are single reports.