CodeSampleX

Recordsnpm@aws-sdk/signature-v4-multi-region3.996.46

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

Current conditions

@aws-sdk/signature-v4-multi-region @3.996.46windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 3 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
39 / 44
Contract verifications
0 / 3
Usage records
12
Independent reporting peers
1
Last recorded
2026-09-01

Dependencies

LibraryVersionMeasured thereProjects
@aws-sdk/types 3.974.5 contract passed 2 project-days
@smithy/signature-v4 5.7.3 contract passed 2 project-days
@smithy/types 4.17.2 contract passed 2 project-days
tslib 2.8.1 contract passed 2 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.996.463.957.0
@aws-sdk/types 3.974.5 3.957.0
@smithy/signature-v4 5.7.3 5.3.8
@smithy/types 4.17.2 4.12.0
@aws-sdk/middleware-sdk-s3 3.957.0
@smithy/protocol-http 5.3.8
tslib 2.8.1 2.8.1

Moved: 3 · unchanged at every release: 3

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