Recordsnpmget-stream
Change the conditions
Current conditions
get-stream @6.0.1ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 5 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
- 16 / 16
- Contract verifications
- 0 / 5
- Usage records
- 4
- Independent reporting peers
- 2
- Last recorded
- 2026-09-14
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 5 passed
Verified — this network ran a contract at this coordinate.
-
get-stream.MaxBufferError
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
5.2.0
windows · node@24.13 · moduleSystem=esm · executionContext=node
31 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.
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.