CodeSampleX

Recordsnpm@aws-sdk/credential-provider-sso3.973.14

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

Current conditions

@aws-sdk/credential-provider-sso @3.973.14windows 11 · x64 · node 24 · npm · node

package-level total, not an API

0 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
0 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-13

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 3

First observed break

3.973.14

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

11 FAIL · stage: UNKNOWN · fingerprint: sha256:e468cae060059622e4ade91273b8b364e6f61349ef50f7f852d3b6bdb53e21b4

Library Version Health Measured there Projects
@aws-sdk/core 3.977.9 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
@aws-sdk/token-providers 3.1116.0 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
@aws-sdk/types 3.974.5 CANDIDATE Correlated change; unproven combination contract passed 21 project-days
@smithy/types 4.17.2 CANDIDATE Correlated change; unproven combination contract passed 20 project-days
@aws-sdk/nested-clients 3.997.44 PASS All observations passed contract passed 21 project-days
@smithy/core 3.33.3 PASS All observations passed contract passed 20 project-days
tslib 2.8.1 PASS All observations passed contract passed 20 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.

Moved: 5 · 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 73 recorded failure clusters. The rest are single reports.