@aws-cdk/aws-s3
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
awscdkconstructss3
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:aws-sdk | AI (typosquat): @aws-cdk/aws-s3 is the official AWS CDK S3 construct library under the @aws-cdk scope — not a typosquat of aws-sdk. The Levenshtein match is a false positive due to scoped namespace comparison. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in CDK Lambda entrypoint is a standard CDK custom resource handler pattern for loading user-provided handlers, not malicious arbitrary module loading. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.204.0 | 6 / 8 |
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.