CodeSampleX

Recordsnpmjsdom29.1.1react.useContext

Change the conditions
Fixed
Symbolreact.useContext
Filter OSalpine musl Runtimenode 22 Package version29.1.1 Architecturex64 Package managernpm Execution contextnode libcmusl Clear filters

Current conditions

react.useContext @29.1.1alpine musl · x64 · node 22 · npm · node

2 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
2 / 2
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-08-18
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 12 · Steady 10

First observed break

29.1.1

linux · node@22.23 · moduleSystem=esm · executionContext=node

2 FAIL · stage: UNKNOWN · fingerprint: sha256:529aac3b1da710068c9dcfe93d0864269e86bebfbe110ca5beeed398860460e7

View exact conditions View failure cluster
Library Version Health Measured there Projects
@asamuzakjp/css-color 5.1.11 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@asamuzakjp/dom-selector 7.1.1 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@csstools/css-syntax-patches-for-csstree 1.1.12 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@csstools/css-syntax-patches-for-csstree 1.1.9 CANDIDATE Correlated change; unproven combination nothing measured 1 project-day
data-urls 7.0.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
html-encoding-sniffer 6.0.0 CANDIDATE Correlated change; unproven combination contract passed 3 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 7.29.1 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 16.0.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@bramus/specificity 2.4.2 PASS All observations passed contract passed 3 project-days
@exodus/bytes 1.15.1 PASS All observations passed contract passed 3 project-days
css-tree 3.2.1 PASS All observations passed contract passed 3 project-days
decimal.js 10.6.0 PASS All observations passed contract passed 3 project-days
is-potential-custom-element-name 1.0.1 PASS All observations passed contract passed 3 project-days
lru-cache 11.5.2 PASS All observations passed contract passed 3 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.

Library30.0.129.1.127.3.026.1.026.0.025.0.124.1.3
@asamuzakjp/css-color 6.0.7 5.1.11 — — — — —
@asamuzakjp/dom-selector 8.3.2 7.1.1 6.7.6 — — — —
@csstools/css-syntax-patches-for-csstree 1.1.12 1.1.9 — — — — —
cssstyle — — 5.3.5 4.6.0 4.6.0 4.6.0 4.6.0
data-urls 7.0.0 7.0.0 6.0.0 5.0.0 5.0.0 5.0.0 5.0.0
html-encoding-sniffer 6.0.0 6.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0
nwsapi — — — 2.2.27 2.2.27 2.2.24 2.2.24
parse5 8.0.1 8.0.1 8.0.0 7.3.0 7.3.0 7.3.0 7.3.0
rrweb-cssom — — — 0.8.0 0.8.0 0.7.1 0.7.1
tough-cookie 6.0.2 6.0.2 6.0.0 5.1.2 5.1.2 5.1.2 —
undici 8.10.2 7.29.1 — — — — —
webidl-conversions 8.0.1 8.0.1 8.0.0 7.0.0 7.0.0 7.0.0 —
whatwg-mimetype 5.0.0 5.0.0 4.0.0 4.0.0 4.0.0 4.0.0 4.0.0
whatwg-url 17.1.0 16.0.1 15.1.0 14.2.0 14.2.0 14.2.0 14.2.0
ws — — 8.18.3 8.21.3 8.21.3 8.21.3 —
@acemir/cssom — — 0.9.30 — — — —
@bramus/specificity 2.4.2 2.4.2 — — — — —
@exodus/bytes 1.15.1 1.15.1 — — — — —
css-tree 3.2.1 3.2.1 — — — — —
decimal.js 10.6.0 10.6.0 10.6.0 10.6.0 10.6.0 10.6.0 10.6.0
form-data — — — — 4.0.6 4.0.6 4.0.6
http-proxy-agent — — 7.0.2 7.0.2 7.0.2 7.0.2 7.0.2
https-proxy-agent — — 7.0.6 7.0.6 7.0.6 7.0.6 7.0.6
is-potential-custom-element-name 1.0.1 1.0.1 1.0.1 1.0.1 1.0.1 1.0.1 1.0.1
lru-cache 11.5.2 11.5.2 — — — — —
saxes 6.0.0 6.0.0 6.0.0 6.0.0 6.0.0 6.0.0 6.0.0
symbol-tree 3.2.4 3.2.4 3.2.4 3.2.4 3.2.4 3.2.4 3.2.4
w3c-xmlserializer 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0
whatwg-encoding — — 3.1.1 3.1.1 3.1.1 3.1.1 3.1.1
xml-name-validator 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0 5.0.0

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.

Recent failure clusters