CodeSampleX

Recordsnpmbare-stream2.13.4

Change the conditions
Fixed
OSdebian glibc Package version2.13.4 Execution contextnode
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm libcglibc Clear filters

Current conditions

bare-stream @2.13.4debian glibc · x64 · node 22 · npm · node

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
4
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

2.13.4

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

9 FAIL · stage: UNKNOWN · fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef

Library Version Health Measured there Projects
b4a 1.8.1 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
b4a 1.9.0 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
streamx 2.28.1 PASS All observations passed contract passed 14 project-days
teex 1.0.1 PASS All observations passed contract passed 14 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.

Moved: 1 · unchanged at every release: 2

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

Showing the 12 most-reported of 26 recorded failure clusters. The rest are single reports.