Recordsnpmreadable-stream
Change the conditions
Current conditions
readable-stream.Duplex @2.3.8x64 · node 22 · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-23
Evidence you can open
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
2 of 2 passed
Observed — real project builds reported from this coordinate.
Dependencies
| Library | Version | Measured there | Projects |
|---|---|---|---|
| core-util-is | 1.0.2 | contract passed | 1 project-day |
| core-util-is | 1.0.3 | contract passed | 9 project-days |
| inherits | 2.0.4 | contract passed | 10 project-days |
| isarray | 1.0.0 | contract passed | 8 project-days |
| process-nextick-args | 2.0.1 | contract passed | 8 project-days |
| safe-buffer | 5.1.2 | contract passed | 7 project-days |
| string_decoder | 1.1.1 | contract passed | 7 project-days |
| util-deprecate | 1.0.2 | contract passed | 7 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.