CodeSampleX

Recordsnpmstreamx

Change the conditions
Fixed
Runtimenode 22 Package version2.28.0 Symbolstreamx.Readable
Filter Architecturex64 Execution contextnode Clear filters

Current conditions

streamx.Readable @2.28.0x64 · node 22 · node

1 of 2 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (1)

Project observations
20 / 31
Contract verifications
1 / 2
Independent reporting peers
3
Failures with a captured fingerprint
0 / 11
Last recorded
2026-08-31
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.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.