CodeSampleX

Recordsnpm@img/sharp-wasm320.35.4

Change the conditions
Fixed
Runtimenode 24 Package version0.35.4
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@img/sharp-wasm32 @0.35.4windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

0.35.4

windows · node@24.13 · moduleSystem=esm · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:61ae78379d96c7fcad024ae19f04b55daa60405f8347cf58c6df9be1daea8c2c

View exact conditions View failure cluster
Library Version Health Measured there Projects
@emnapi/runtime 1.11.3 CANDIDATE Correlated change; unproven combination 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.

Library0.35.40.35.20.34.5
@emnapi/runtime 1.11.3 1.11.3 1.7.1

Moved: 1 · unchanged at every release: 0

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