CodeSampleX

Compatibilitynpmreadable-stream3.6.2

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

Current conditions

readable-stream @3.6.2windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

8 of 10 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
8 / 10
Contract verifications
nothing at this coordinate
Usage records
13
Independent reporting peers
1
Failures with a captured fingerprint
0 / 2
Last recorded
2026-08-21
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
inherits 2.0.4 contract passed 5 project-days
string_decoder 1.3.0 contract passed 5 project-days
util-deprecate 1.0.2 contract passed 5 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