Recordsnpmstring_decoder
Change the conditions
Current conditions
string_decoder @1.3.0ubuntu 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 (2)
- Project observations
- 55 / 57
- Contract verifications
- 0 / 57
- Usage records
- 89
- Independent reporting peers
- 3
- Failures with a captured fingerprint
- 0 / 2
- Last recorded
- 2026-09-07
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
0 of 57 passed
Verified — this network ran a contract at this coordinate.
-
string_decoder.StringDecoder
2 of 2 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.3.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
16 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| safe-buffer | 5.2.1 | CANDIDATE Correlated change; unproven combination | contract passed | 37 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.
| Library | 1.3.0 | 1.1.1 |
|---|---|---|
| safe-buffer | 5.2.1 | 5.1.2 |
Moved: 1 · unchanged at every release: 0
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.