Recordsnpmjsdom
Change the conditions
Current conditions
jsdom @29.1.1ubuntu 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
- 2 / 2
- Contract verifications
- 0 / 4
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
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.
-
jsdom.JSDOM
0 of 4 passed
Verified — this network ran a contract at this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| @asamuzakjp/css-color | 5.1.11 | contract passed | 1 project-day |
| @asamuzakjp/dom-selector | 7.1.1 | contract passed | 1 project-day |
| @bramus/specificity | 2.4.2 | contract passed | 1 project-day |
| @csstools/css-syntax-patches-for-csstree | 1.1.9 | nothing measured | 1 project-day |
| @exodus/bytes | 1.15.1 | contract passed | 1 project-day |
| css-tree | 3.2.1 | contract passed | 1 project-day |
| data-urls | 7.0.0 | contract passed | 1 project-day |
| decimal.js | 10.6.0 | contract passed | 1 project-day |
| html-encoding-sniffer | 6.0.0 | contract passed | 1 project-day |
| is-potential-custom-element-name | 1.0.1 | contract passed | 1 project-day |
| lru-cache | 11.5.2 | contract passed | 1 project-day |
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.