@pulumi/eks
[](https://github.com/pulumi/pulumi-eks/actions/workflows/master.yml) [](https://slack.pulumi.com) [![n
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @pulumi/eks is a scoped package under the official Pulumi namespace; Levenshtein similarity to 'qs' is a mechanical false positive with no squatting intent. | ai | |
| phantom-deps | phantom-dep:which | AI (phantom-deps): Listed as a legitimate runtime dependency in package.json; phantom detection is a false positive for this Pulumi provider package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Listed as a legitimate runtime dependency in package.json; phantom detection is a false positive for this Pulumi provider package. | ai | |
| phantom-deps | phantom-dep:js-yaml | AI (phantom-deps): Listed as a legitimate runtime dependency in package.json; phantom detection is a false positive for this Pulumi provider package. | ai | |
| phantom-deps | phantom-dep:netmask | AI (phantom-deps): Listed as a legitimate runtime dependency in package.json; phantom detection is a false positive for this Pulumi provider package. | ai | |
| phantom-deps | phantom-dep:https-proxy-agent | AI (phantom-deps): Listed as a legitimate runtime dependency in package.json; phantom detection is a false positive for this Pulumi provider package. | ai | |
| dependencies | unvetted-dep:@pulumi/aws | AI (dependencies): @pulumi/aws is the official Pulumi AWS provider, a major well-known package; unvetted flag is a pipeline artifact. | ai |
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
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.