@smithy/credential-provider-imds
AWS credential provider that sources credentials from the EC2 instance metadata service and ECS container metadata service
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from smithy-team to GitHub Actions CI/CD publishing, confirmed by SLSA provenance attestation. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared dep used implicitly by TypeScript compilation output. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 4.4.9 | 3 / 5 | |
| 4.4.8 | 3 / 5 | |
| 4.4.7 | 3 / 5 | |
| 4.4.6 | 3 / 5 | |
| 4.4.5 | 3 / 5 | |
| 4.4.4 | 3 / 5 | |
| 4.4.3 | 3 / 5 | |
| 4.4.2 | 3 / 5 | |
| 4.4.1 | 3 / 5 | |
| 4.4.0 | 3 / 5 | |
| 4.3.9 | 3 / 5 | |
| 4.3.8 | 3 / 5 | |
| 4.3.7 | 3 / 5 | |
| 4.3.6 | 3 / 5 | |
| 4.3.5 | 3 / 5 | |
| 4.3.4 | 3 / 5 | |
| 4.3.3 | 3 / 5 | |
| 4.3.2 | 3 / 5 | |
| 4.3.1 | 3 / 5 | |
| 4.3.0 | 3 / 5 | |
| 4.2.14 | 5 / 5 | |
| 4.2.13 | 5 / 5 | |
| 4.2.12 | 5 / 5 | |
| 4.2.11 | 5 / 5 | |
| 4.2.10 | 5 / 5 | |
| 4.2.9 | 5 / 5 | |
| 4.2.8 | 5 / 5 | |
| 4.2.7 | 5 / 5 | |
| 4.2.6 | 5 / 5 | |
| 4.2.5 | 5 / 5 | |
| 4.2.4 | 5 / 5 | |
| 4.2.3 | 5 / 5 | |
| 4.2.2 | 5 / 5 | |
| 4.2.1 | 5 / 5 | |
| 4.2.0 | 5 / 5 | |
| 4.1.2 | 5 / 5 | |
| 4.1.1 | 5 / 5 | |
| 4.1.0 | 5 / 5 | |
| 4.0.7 | 5 / 5 | |
| 4.0.6 | 5 / 5 | |
| 4.0.5 | 5 / 5 | |
| 4.0.4 | 5 / 5 | |
| 4.0.3 | 5 / 5 | |
| 4.0.2 | 5 / 5 | |
| 4.0.1 | 5 / 5 | |
| 4.0.0 | 5 / 5 |
v4.4.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.7
2 findingsThis version was published by a different npm account than previous versions on 2026-06-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.