CodeSampleX

Recordsnpmparse-json8.3.0

Change the conditions
Fixed
OSubuntu glibc Package version8.3.0 Package manageryarn 4
Filter Runtimenode 22 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

parse-json @8.3.0ubuntu glibc · x64 · node 22 · yarn 4 · node

package-level total, not an API

4 of 4 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
4 / 4
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-07

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

8.3.0

linux · node@22.23 · executionContext=node · moduleSystem=cjs

3 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

Library Version Health Measured there Projects
@babel/code-frame 7.29.7 PASS All observations passed contract passed 2 project-days
index-to-position 1.2.0 PASS All observations passed contract passed 2 project-days
type-fest 4.41.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.

Moved: 0 · unchanged at every release: 7

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