@aws-cdk/aws-lambda
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
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
romainmulleramzn-ossrix0rrraws-cdk-team
Keywords
awscdkconstructslambda
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@aws-cdk/aws-events | AI (phantom-deps): Sibling @aws-cdk/* package in the CDK monorepo; declared but not directly imported is a common monorepo artifact, not a security concern for this package. | ai | |
| provenance | no-provenance | AI (provenance): aws-cdk-team is a well-established AWS publisher; lack of Sigstore provenance is expected for packages of this age and is not a security concern here. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.204.0 | 20 / 12 |
v1.204.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.