CodeSampleX

Recordsnpmstreamx2.28.0

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

Current conditions

streamx @2.28.0windows 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 (2)

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
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

2.28.0

executionContext=node

18 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
events-universal 1.0.1 PASS All observations passed contract passed 14 project-days
fast-fifo 1.3.2 PASS All observations passed contract passed 13 project-days
text-decoder 1.2.7 PASS All observations passed contract passed 11 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.

Library2.28.12.28.0
events-universal 1.0.1 1.0.1
fast-fifo 1.3.2 1.3.2
text-decoder 1.2.7 1.2.7

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.

Recent failure clusters