CodeSampleX

Recordsnpmbare-stream2.13.3

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

Current conditions

bare-stream @2.13.3windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

15 of 20 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 (14)

Project observations
15 / 20
Contract verifications
nothing at this coordinate
Usage records
3
Independent reporting peers
1
Failures with a captured fingerprint
0 / 5
Last recorded
2026-08-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 3

First observed break

2.13.3

executionContext=node

18 FAIL · stage: PROJECT_PROCESS

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