CodeSampleX

Recordsnpm@jest/schemas30.4.1

Change the conditions
Fixed
Runtimenode 22 Package version30.4.1 Package managernpm
Filter OSdebian glibc Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@jest/schemas @30.4.1debian glibc · x64 · node 22 · npm · node

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
7
Independent reporting peers
1
Last recorded
2026-09-06

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

30.4.1

linux · node@22.23 · executionContext=node

3 FAIL · stage: UNKNOWN · fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2

Library Version Health Measured there Projects
@sinclair/typebox 0.34.52 CANDIDATE Correlated change; unproven combination contract passed 65 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.

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