CodeSampleX

Recordsnpmwebcrypto-core1.9.2

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

Current conditions

webcrypto-core @1.9.2ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 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 failed

Project observations
9 / 10
Contract verifications
0 / 2
Independent reporting peers
3
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 7

First observed break

1.9.2

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

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

Library Version Health Measured there Projects
@peculiar/asn1-schema 2.8.0 PASS All observations passed contract passed 6 project-days
@peculiar/asn1-schema 2.9.3 PASS All observations passed contract passed 2 project-days
@peculiar/asn1-schema 2.9.4 PASS All observations passed contract passed 3 project-days
@peculiar/json-schema 1.1.12 PASS All observations passed contract passed 10 project-days
@peculiar/utils 2.0.3 PASS All observations passed contract passed 10 project-days
asn1js 3.0.10 PASS All observations passed contract passed 9 project-days
tslib 2.8.1 PASS All observations passed contract passed 9 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