CodeSampleX

Recordsnpmtar-stream2.2.0

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

Current conditions

tar-stream @2.2.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 (3)

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 · Steady 5

First observed break

2.2.0

linux · node@22.23 · moduleSystem=cjs · executionContext=node

5 FAIL · stage: UNKNOWN · fingerprint: sha256:986d98189e70ab6bb81e3ca5f5feb96281ba0dfa6e522caa6ddd3d9b148578cc

View exact conditions View failure cluster
Library Version Health Measured there Projects
bl 4.1.0 PASS All observations passed contract passed 23 project-days
end-of-stream 1.4.5 PASS All observations passed contract passed 24 project-days
fs-constants 1.0.0 PASS All observations passed contract passed 21 project-days
inherits 2.0.4 PASS All observations passed contract passed 24 project-days
readable-stream 3.6.2 PASS All observations passed contract passed 23 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.2.13.2.02.2.0
b4a 1.8.1 1.9.0 —
bare-fs 4.8.1 4.8.1 —
bl — — 4.1.0
end-of-stream — — 1.4.5
fast-fifo 1.3.2 1.3.2 —
fs-constants — — 1.0.0
inherits — — 2.0.4
readable-stream — — 3.6.2
streamx 2.28.1 2.28.1 —

Moved: 1 · unchanged at every release: 8

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