CodeSampleX

Recordsnpm@aws-sdk/credential-provider-login3.958.0

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

Current conditions

@aws-sdk/credential-provider-login @3.958.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

Dependencies

LibraryVersionMeasured thereProjects
@aws-sdk/core 3.957.0 contract passed 1 project-day
@aws-sdk/nested-clients 3.958.0 contract passed 1 project-day
@aws-sdk/types 3.957.0 contract passed 1 project-day
@smithy/property-provider 4.2.8 contract passed 1 project-day
@smithy/protocol-http 5.3.8 contract passed 1 project-day
@smithy/shared-ini-file-loader 4.4.3 contract passed 1 project-day
@smithy/types 4.12.0 contract passed 1 project-day
tslib 2.8.1 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.

Library3.972.773.972.23.962.03.958.0
@aws-sdk/core 3.977.9 3.973.3 3.957.0 3.957.0
@aws-sdk/nested-clients 3.997.44 3.975.0 3.958.0 3.958.0
@aws-sdk/types 3.974.5 3.973.1 3.957.0 3.957.0
@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/protocol-http 5.3.8 5.3.8 5.3.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: 4 · unchanged at every release: 5

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.