CodeSampleX

Recordsnpm@aws-sdk/core3.957.0

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

Current conditions

@aws-sdk/core @3.957.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
20 / 52
Contract verifications
0 / 9
Usage records
45
Independent reporting peers
1
Last recorded
2026-09-15
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 8

First observed break

3.957.0

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

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0d787687eb6d91ecda01dd52049f201fdea94afc8d0ee8e9241b7bad335978fa

View exact conditions View failure cluster
Library Version Health Measured there Projects
@aws-sdk/types 3.957.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@aws-sdk/xml-builder 3.957.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@smithy/core 3.22.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@smithy/signature-v4 5.3.8 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@smithy/types 4.12.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@smithy/node-config-provider 4.3.8 PASS All observations passed contract passed 2 project-days
@smithy/property-provider 4.2.8 PASS All observations passed contract passed 1 project-day
@smithy/protocol-http 5.3.8 PASS All observations passed contract passed 2 project-days
@smithy/smithy-client 4.11.1 PASS All observations passed contract passed 2 project-days
@smithy/util-base64 4.3.0 PASS All observations passed contract passed 2 project-days
@smithy/util-middleware 4.2.8 PASS All observations passed contract passed 1 project-day
@smithy/util-utf8 4.2.0 PASS All observations passed contract passed 1 project-day
tslib 2.8.1 PASS All observations passed 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.

Library3.977.93.973.33.957.0
@aws-sdk/types 3.974.5 3.973.1 3.957.0
@aws-sdk/xml-builder 3.972.40 3.972.2 3.957.0
@smithy/core 3.33.3 3.22.0 3.22.0
@smithy/signature-v4 5.7.3 5.3.8 5.3.8
@smithy/types 4.17.2 4.12.0 4.12.0
@aws/lambda-invoke-store 0.3.0 — —
@smithy/node-config-provider — 4.3.8 4.3.8
@smithy/property-provider — 4.2.8 4.2.8
@smithy/protocol-http — 5.3.8 5.3.8
@smithy/smithy-client — 4.11.1 4.11.1
@smithy/util-base64 — 4.3.0 4.3.0
@smithy/util-middleware — 4.2.8 4.2.8
@smithy/util-utf8 — 4.2.0 4.2.0
bowser 2.14.1 — —
tslib 2.8.1 2.8.1 2.8.1

Moved: 5 · unchanged at every release: 10

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