Recordsnpmbare-stream
Change the conditions
Current conditions
bare-stream.isEnded @2.13.3x64 · 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
- 23 / 34
- Contract verifications
- 1 / 2
- Independent reporting peers
- 3
- Failures with a captured fingerprint
- 0 / 11
- Last recorded
- 2026-08-31
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| b4a | 1.8.1 | contract passed | 5 project-days |
| streamx | 2.28.1 | contract passed | 3 project-days |
| teex | 1.0.1 | contract passed | 3 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: 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.