@aws-sdk/credential-providers
A collection of credential providers, without requiring service clients like STS, Cognito
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:credential-dir-access | AI (semgrep): This package IS a credential provider; accessing ~/.aws/credentials is its core documented purpose. The flagged code is a JSDoc comment example, not malicious harvesting. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/util-credentials | AI (phantom-deps): Framework-scoped AWS SDK package loaded by convention in the credential provider chain; not a security concern. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/shared-ini-file-loader | AI (phantom-deps): Framework-scoped AWS SDK package loaded by convention in the credential provider chain; not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): AWS SDK bot publishes hundreds of packages without Sigstore provenance; this is consistent across the entire aws-sdk-js-v3 ecosystem and not a risk signal. | ai | |
| dependencies | unvetted-dep:@aws-sdk/credential-provider-cognito-identity | AI (dependencies): @aws-sdk/credential-provider-cognito-identity is a first-party AWS SDK v3 package from the same monorepo, published by the same trusted aws-sdk-bot publisher. | ai |
Versions (showing 51 of 557)
| Version | Deps | Published |
|---|---|---|
| 3.1057.0 | 17 / 6 | |
| 3.1056.0 | 17 / 6 | |
| 3.1055.0 | 17 / 6 | |
| 3.1054.0 | 17 / 6 | |
| 3.1053.0 | 17 / 6 | |
| 3.1052.0 | 17 / 6 | |
| 3.1051.0 | 17 / 6 | |
| 3.1050.0 | 17 / 6 | |
| 3.1049.0 | 17 / 6 | |
| 3.1048.0 | 17 / 6 | |
| 3.1047.0 | 17 / 6 | |
| 3.1046.0 | 17 / 6 | |
| 3.1045.0 | 20 / 6 | |
| 3.1044.0 | 20 / 6 | |
| 3.1043.0 | 20 / 6 | |
| 3.1042.0 | 20 / 6 | |
| 3.1041.0 | 20 / 6 | |
| 3.1040.0 | 20 / 6 | |
| 3.1039.0 | 20 / 6 | |
| 3.1038.0 | 20 / 6 | |
| 3.1037.0 | 20 / 6 | |
| 3.1036.0 | 20 / 6 | |
| 3.1035.0 | 20 / 6 | |
| 3.1034.0 | 20 / 6 | |
| 3.1033.0 | 20 / 6 | |
| 3.1032.0 | 20 / 6 | |
| 3.1031.0 | 20 / 6 | |
| 3.1030.0 | 20 / 6 | |
| 3.1029.0 | 20 / 6 | |
| 3.1028.0 | 20 / 6 | |
| 3.1027.0 | 20 / 6 | |
| 3.1026.0 | 20 / 6 | |
| 3.1025.0 | 20 / 6 | |
| 3.1024.0 | 20 / 6 | |
| 3.1023.0 | 20 / 6 | |
| 3.1022.0 | 20 / 6 | |
| 3.1021.0 | 20 / 6 | |
| 3.1020.0 | 20 / 6 | |
| 3.1019.0 | 20 / 6 | |
| 3.1018.0 | 20 / 6 | |
| 3.1017.0 | 20 / 6 | |
| 3.1016.0 | 20 / 6 | |
| 3.1015.0 | 20 / 6 | |
| 3.1014.0 | 20 / 6 | |
| 3.1013.0 | 20 / 6 | |
| 3.1012.0 | 20 / 6 | |
| 3.1011.0 | 20 / 6 | |
| 3.1010.0 | 20 / 6 | |
| 3.1009.0 | 20 / 6 | |
| 3.1008.0 | 20 / 6 | |
| 3.1007.0 | 20 / 6 |
v3.1057.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1056.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1055.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1054.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1053.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1052.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1051.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1050.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1049.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1048.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1047.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1046.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1045.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1044.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1043.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1042.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1041.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1040.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1039.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1038.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1037.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1036.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1035.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.