CodeSampleX

Recordsnpmarchiver5.3.2

Change the conditions
Fixed
Runtimenode 24 Package version5.3.2
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

archiver @5.3.2windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 11 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
25 / 28
Contract verifications
0 / 11
Usage records
46
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 7

First observed break

5.3.2

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

3 FAIL · stage: UNKNOWN · fingerprint: sha256:c113861ea6575a55f8e3a44f91634852da7cbcd3825a7f52264c417b812b7599

Library Version Health Measured there Projects
archiver-utils 2.1.0 PASS All observations passed contract passed 16 project-days
async 3.2.6 PASS All observations passed contract passed 16 project-days
buffer-crc32 0.2.13 PASS All observations passed contract passed 16 project-days
readable-stream 3.6.2 PASS All observations passed contract passed 16 project-days
readdir-glob 1.1.3 PASS All observations passed contract passed 16 project-days
tar-stream 2.2.0 PASS All observations passed contract passed 16 project-days
zip-stream 4.1.1 PASS All observations passed contract passed 16 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