Recordsnpmjsdom30.0.1CookieJar
Change the conditions
Current conditions
CookieJar @30.0.1windows 11 · x64 · node 24 · npm 11 · node
1 of 1 passed
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
- 1 / 1
- Contract verifications
- nothing at this coordinate
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Dependency Health
Observed combinations and failure evidence for this release
First observed break
30.0.1
linux · node@22.23 · executionContext=node · moduleSystem=cjs
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:f0ffff252e3f94518ed1f8821bf9fcf877e30b2d5cf79818540559f03f269589
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @asamuzakjp/css-color | 6.0.7 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| @asamuzakjp/dom-selector | 8.3.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| @csstools/css-syntax-patches-for-csstree | 1.1.12 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| data-urls | 7.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| html-encoding-sniffer | 6.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| parse5 | 8.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| tough-cookie | 6.0.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| undici | 8.10.2 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| webidl-conversions | 8.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| whatwg-mimetype | 5.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| whatwg-url | 17.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| @bramus/specificity | 2.4.2 | PASS All observations passed | contract passed | 2 project-days |
| @exodus/bytes | 1.15.1 | PASS All observations passed | contract passed | 2 project-days |
| css-tree | 3.2.1 | PASS All observations passed | contract passed | 2 project-days |
| decimal.js | 10.6.0 | PASS All observations passed | contract passed | 2 project-days |
| is-potential-custom-element-name | 1.0.1 | PASS All observations passed | contract passed | 2 project-days |
| lru-cache | 11.5.2 | PASS All observations passed | contract passed | 2 project-days |
| saxes | 6.0.0 | PASS All observations passed | contract passed | 2 project-days |
| symbol-tree | 3.2.4 | PASS All observations passed | contract passed | 2 project-days |
| w3c-xmlserializer | 5.0.0 | PASS All observations passed | contract passed | 2 project-days |
| xml-name-validator | 5.0.0 | PASS All observations passed | contract passed | 2 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: 15 · unchanged at every release: 15
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.