CodeSampleX

Recordsnpm@smithy/util-buffer-from2.2.0

Change the conditions
Fixed
OSwindows 11 Package version2.2.0 Package managernpm 11
Filter Runtimenode 24 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@smithy/util-buffer-from @2.2.0windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 9 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
19 / 66
Contract verifications
0 / 9
Usage records
45
Independent reporting peers
1
Last recorded
2026-09-01

Dependency Health

Observed problems 2 · Steady 0

First observed break

2.2.0 @smithy/is-array-buffer@2.2.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

Library Version Health Measured there Projects
@smithy/is-array-buffer 2.2.0 FAIL Linked failure observed; version changed across releases contract passed 1 project-day
tslib 2.8.1 FAIL Linked failure observed on this release contract passed 1 project-day

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.

Library4.2.02.2.0
@smithy/is-array-buffer 4.2.0 2.2.0
tslib 2.8.1 2.8.1

Moved: 1 · unchanged at every release: 1

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 27 recorded failure clusters. The rest are single reports.