CodeSampleX

Recordsnpmparse-json5.2.0

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

Current conditions

parse-json @5.2.0debian 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.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-07
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 4

First observed break

5.2.0

moduleSystem=esm · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
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.

Library8.3.05.2.04.0.0
@babel/code-frame 7.29.7 7.29.7 —
error-ex — 1.3.4 1.3.4
index-to-position 1.2.0 — —
json-parse-better-errors — — 1.0.2
json-parse-even-better-errors — 2.3.1 —
lines-and-columns — 1.2.4 —
type-fest 4.41.0 — —

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