CodeSampleX

Recordsnpmparse-json5.2.0parseJson

Change the conditions
Fixed
SymbolparseJson Architecturex64
Filter OSalpine musl Runtimenode 22 Package version5.2.0 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

parseJson @5.2.0alpine musl · x64 · node 22 · npm · node

1 of 1 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
1 / 1
Last recorded
2026-08-23

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 4

First observed break

5.2.0

executionContext=node · moduleSystem=esm

6 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
@babel/code-frame 7.29.7 PASS All observations passed contract passed 16 project-days
error-ex 1.3.4 PASS All observations passed contract passed 16 project-days
json-parse-even-better-errors 2.3.1 PASS All observations passed contract passed 15 project-days
lines-and-columns 1.2.4 PASS All observations passed contract passed 16 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