CodeSampleX

Recordsnpmreadable-stream2.3.8readable-stream.Readable

Change the conditions
Fixed
Symbolreadable-stream.Readable Package managernpm
Filter OSalpine musl Runtimenode 22 Package version2.3.8 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

readable-stream.Readable @2.3.8alpine musl · x64 · node 22 · npm · node

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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-23
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 7

First observed break

2.3.8

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
string_decoder 1.1.1 CANDIDATE Correlated change; unproven combination contract passed 30 project-days
core-util-is 1.0.2 PASS All observations passed contract passed 15 project-days
core-util-is 1.0.3 PASS All observations passed contract passed 20 project-days
inherits 2.0.4 PASS All observations passed contract passed 34 project-days
isarray 1.0.0 PASS All observations passed contract passed 29 project-days
process-nextick-args 2.0.1 PASS All observations passed contract passed 30 project-days
safe-buffer 5.1.2 PASS All observations passed contract passed 30 project-days
util-deprecate 1.0.2 PASS All observations passed contract passed 29 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.6.22.3.8
string_decoder 1.3.0 1.1.1
core-util-is — 1.0.2
inherits 2.0.4 2.0.4
isarray — 1.0.0
process-nextick-args — 2.0.1
safe-buffer — 5.1.2
util-deprecate 1.0.2 1.0.2

Moved: 1 · unchanged at every release: 6

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