CodeSampleX

Recordsnpmstring_decoder1.3.0string_decoder.StringDecoder

Change the conditions
Fixed
OSubuntu glibc Package version1.3.0 Symbolstring_decoder.StringDecoder
Filter Runtimenode 22 Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

string_decoder.StringDecoder @1.3.0ubuntu glibc · x64 · node 22 · npm 10 · node

2 of 2 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-23

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

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.

Library1.3.01.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.

Recent failure clusters

Showing the 12 most-reported of 28 recorded failure clusters. The rest are single reports.