Recordsnpmparse-json
Change the conditions
Current conditions
parse-json @5.2.0ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 5 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate failed (1)
- Project observations
- 19 / 21
- Contract verifications
- 0 / 5
- Usage records
- 3
- Independent reporting peers
- 3
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-09-14
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 5 passed
Verified — this network ran a contract at this coordinate.
-
parse-json.JSONError
2 of 3 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.2.0
moduleSystem=esm · executionContext=node
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.
| Library | 8.3.0 | 5.2.0 | 4.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.