CodeSampleX

Recordsnpmstreamx

Change the conditions
Fixed
Package version2.28.1 Package managernpm 10 Execution contextnode
Filter OSubuntu glibc Runtimenode 22 Architecturex64 libcglibc Clear filters

Current conditions

streamx @2.28.1ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 57 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
110 / 110
Contract verifications
0 / 57
Usage records
75
Independent reporting peers
3
Last recorded
2026-09-17
Evidence you can open

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 3

First observed break

2.28.1

linux · node@22.23 · executionContext=node

8 FAIL · stage: UNKNOWN · fingerprint: sha256:cc724e2e6a3269f972e9240542370fc6cb5ed829cb14a86221d7aa2e4a3e210a

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