Recordsnpmparse-json
Change the conditions
Current conditions
parse-json @5.2.0ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 4 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
- 15 / 17
- Contract verifications
- 0 / 4
- Usage records
- 2
- Independent reporting peers
- 3
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-08-31
Evidence you can open
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 4 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.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @babel/code-frame | 7.29.7 | contract passed | 5 project-days |
| error-ex | 1.3.4 | contract passed | 5 project-days |
| json-parse-even-better-errors | 2.3.1 | contract passed | 5 project-days |
| lines-and-columns | 1.2.4 | contract passed | 5 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.