@pulumi/aws
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/aws is a major scoped package; Levenshtein match to 'qs' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): @pulumi/aws is a major scoped package; Levenshtein match to 'ajv' is a false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard CloudWatch log event decoding (base64+gunzip); no malicious payload. | ai | |
| semgrep | semgrep:ssh-key-access | AI (semgrep): Fires on a JSDoc example showing ~/.ssh/id_rsa.pub; not credential theft. | ai | |
| phantom-deps | phantom-dep:mime | AI (phantom-deps): mime is a declared runtime dep; phantom-dep heuristic is a false positive here. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 169.254.169.254 is the AWS instance metadata endpoint, used in a shell script example in JSDoc. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Fires on `new Function(...)` where Function is the class being defined, not eval-like dynamic code execution. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.32.0 | 2 / 3 | |
| 7.31.0 | 2 / 3 | |
| 7.30.0 | 2 / 3 | |
| 7.29.0 | 2 / 3 | |
| 7.28.0 | 2 / 3 | |
| 7.27.0 | 2 / 3 | |
| 7.26.0 | 2 / 3 | |
| 7.25.0 | 2 / 3 | |
| 7.24.0 | 2 / 3 | |
| 6.83.4 | 2 / 3 | |
| 6.83.3 | 2 / 3 |
v7.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
2 findingsAccessing SSH keys — strong indicator of credential theft Source: https://github.com/pulumi/pulumi-aws/blob/d175b0aabffdf982839ee90452f06020ecc55750/lightsail/keyPair.js#L46 44 | * name: "example", 45 | * publicKey: std.file({ > 46 | * input: "~/.ssh/id_rsa.pub", 47 | * }).then(invoke => invoke.result), 48 | * });
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.0
2 findingsAccessing SSH keys — strong indicator of credential theft Source: https://github.com/pulumi/pulumi-aws/blob/9a278c11da0b98c0f2ee16d285a888318f7c5957/lightsail/keyPair.js#L46 44 | * name: "example", 45 | * publicKey: std.file({ > 46 | * input: "~/.ssh/id_rsa.pub", 47 | * }).then(invoke => invoke.result), 48 | * });
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.83.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.83.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.