CodeSampleX

Recordsnpm@aws-sdk/credential-provider-node3.972.81

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

Current conditions

@aws-sdk/credential-provider-node @3.972.81windows 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/credential-provider-env 3.972.70 contract passed 2 project-days
@aws-sdk/credential-provider-http 3.972.72 contract passed 2 project-days
@aws-sdk/credential-provider-ini 3.973.15 contract passed 2 project-days
@aws-sdk/credential-provider-process 3.972.70 contract passed 2 project-days
@aws-sdk/credential-provider-sso 3.973.14 contract passed 2 project-days
@aws-sdk/credential-provider-web-identity 3.972.76 contract passed 1 project-day
@aws-sdk/types 3.974.5 contract passed 2 project-days
@smithy/core 3.33.3 contract passed 2 project-days
@smithy/credential-provider-imds 4.5.2 contract passed 1 project-day
@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.972.813.972.23.962.03.958.0
@aws-sdk/credential-provider-env 3.972.70 3.972.2 3.957.0 3.957.0
@aws-sdk/credential-provider-http 3.972.72 3.972.3 3.957.0 3.957.0
@aws-sdk/credential-provider-ini 3.973.15 3.972.2 3.962.0 3.958.0
@aws-sdk/credential-provider-process 3.972.70 3.972.2 3.957.0 3.957.0
@aws-sdk/credential-provider-sso 3.973.14 3.972.2 3.958.0 3.958.0
@aws-sdk/credential-provider-web-identity 3.972.76 3.972.2 3.958.0 3.958.0
@aws-sdk/types 3.974.5 3.973.1 3.957.0 3.957.0
@smithy/credential-provider-imds 4.5.2 4.2.8 4.2.8 4.2.8
@smithy/types 4.17.2 4.12.0 4.12.0 4.12.0
@smithy/core 3.33.3
@smithy/property-provider 4.2.8 4.2.8 4.2.8
@smithy/shared-ini-file-loader 4.4.3 4.4.3 4.4.3
tslib 2.8.1 2.8.1 2.8.1 2.8.1

Moved: 9 · unchanged at every release: 4

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