CodeSampleX

Recordsnpmparse-json5.2.0parse-json.JSONError

Change the conditions
Fixed
Symbolparse-json.JSONError Architecturex64
Filter OSubuntu glibc Runtimenode 22 Package version5.2.0 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

parse-json.JSONError @5.2.0ubuntu glibc · x64 · node 22 · npm 10 · node

2 of 3 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 3
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-29

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