CodeSampleX

Recordsnpmarchiver-utils2.1.0

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

Current conditions

archiver-utils @2.1.0windows 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 (1)

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
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 9

First observed break

2.1.0

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
readable-stream 2.3.8 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
glob 7.2.3 PASS All observations passed contract passed 17 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 17 project-days
lazystream 1.0.1 PASS All observations passed contract passed 17 project-days
lodash.defaults 4.2.0 PASS All observations passed contract passed 17 project-days
lodash.difference 4.5.0 PASS All observations passed contract passed 17 project-days
lodash.flatten 4.4.0 PASS All observations passed contract passed 17 project-days
lodash.isplainobject 4.0.6 PASS All observations passed contract passed 17 project-days
lodash.union 4.6.0 PASS All observations passed contract passed 16 project-days
normalize-path 3.0.0 PASS All observations passed contract passed 17 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.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Library3.0.42.1.0
readable-stream 3.6.2 2.3.8
glob 7.2.3 7.2.3
graceful-fs 4.2.11 4.2.11
lazystream 1.0.1 1.0.1
lodash.defaults 4.2.0 4.2.0
lodash.difference 4.5.0 4.5.0
lodash.flatten 4.4.0 4.4.0
lodash.isplainobject 4.0.6 4.0.6
lodash.union 4.6.0 4.6.0
normalize-path 3.0.0 3.0.0

Moved: 1 · unchanged at every release: 9

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters