CodeSampleX

Recordsnpm@peculiar/webcrypto1.7.1

Change the conditions
Fixed
Runtimenode (version not recorded) Package managernpm
Filter OSwindows 11 Package version1.7.1 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@peculiar/webcrypto @1.7.1windows 11 · x64 · node (version not recorded) · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

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
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 7

First observed break

1.7.1

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@peculiar/asn1-schema 2.8.0 PASS All observations passed contract passed 7 project-days
@peculiar/asn1-schema 2.9.3 PASS All observations passed contract passed 5 project-days
@peculiar/asn1-schema 2.9.4 PASS All observations passed contract passed 2 project-days
@peculiar/json-schema 1.1.12 PASS All observations passed contract passed 13 project-days
@peculiar/utils 2.0.3 PASS All observations passed contract passed 13 project-days
tslib 2.8.1 PASS All observations passed contract passed 13 project-days
webcrypto-core 1.9.2 PASS All observations passed contract passed 13 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.