CodeSampleX

Recordsnpmside-channel-weakmap1.0.2

Change the conditions
Fixed
Runtimenode 22 Package managernpm 10
Filter OSubuntu glibc Package version1.0.2 Symbolwhole package Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

side-channel-weakmap @1.0.2ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 8 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
73 / 75
Contract verifications
0 / 8
Usage records
44
Independent reporting peers
1
Failures with a captured fingerprint
1 / 2
Last recorded
2026-10-21

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 5

First observed break

1.0.2

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

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

Library Version Health Measured there Projects
call-bound 1.0.4 PASS All observations passed contract passed 89 project-days
es-errors 1.3.0 PASS All observations passed contract passed 89 project-days
get-intrinsic 1.3.0 PASS All observations passed contract passed 88 project-days
object-inspect 1.13.4 PASS All observations passed contract passed 89 project-days
side-channel-map 1.0.1 PASS All observations passed contract passed 89 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.

Recent failure clusters