CodeSampleX

Recordsnpmpkijs3.4.0

Change the conditions
Fixed
Runtimenode 22 Package managernpm
Filter OSalpine musl Package version3.4.0 Symbolwhole package Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

pkijs @3.4.0alpine musl · x64 · node 22 · npm · node

package-level total, not an API

1 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 came back clean (1)

Project observations
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-09-05

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 7

First observed break

3.4.0

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

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

Library Version Health Measured there Projects
@noble/hashes 1.4.0 PASS All observations passed contract passed 13 project-days
asn1js 3.0.10 PASS All observations passed contract passed 13 project-days
bytestreamjs 2.0.1 PASS All observations passed contract passed 13 project-days
pvtsutils 1.3.6 PASS All observations passed contract passed 12 project-days
pvutils 1.1.5 PASS All observations passed contract passed 5 project-days
pvutils 1.2.0 PASS All observations passed contract passed 8 project-days
tslib 2.8.1 PASS All observations passed contract passed 12 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