CodeSampleX

Recordsnpmpkijs3.4.0

Change the conditions
Fixed
Runtimenode 22 Package managernpm 11
Filter OSwindows 11 Package version3.4.0 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

pkijs @3.4.0windows 11 · x64 · node 22 · npm 11 · node

package-level total, not an API

18 of 19 passed

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
18 / 19
Contract verifications
nothing at this coordinate
Usage records
5
Independent reporting peers
1
Failures with a captured fingerprint
0 / 1
Last recorded
2026-08-24
Evidence you can open

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

View exact conditions View failure cluster
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