CodeSampleX

Recordsnpmget-stream6.0.1

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

Current conditions

get-stream @6.0.1windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

1 of 1 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
1 / 1
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

5.2.0

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

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

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.

Library9.0.15.2.0
@sec-ant/readable-stream 0.4.1 —
is-stream 4.0.1 —
pump — 3.0.4

Moved: 0 · unchanged at every release: 3

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.