@aws-cdk/aws-s3 No license 40 versions

@aws-cdk/aws-s3

npm Repository Homepage

40

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, so a manually published version cannot be tied back to a reviewed commit.

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
npm-metadata	url-dep:cfn2ts	AI (npm-metadata): Monorepo devDependency, internal build tool, not external risk.	ai	2026/07/21
npm-metadata	url-dep:cdk-integ-tools	AI (npm-metadata): Monorepo devDependency, internal build tool, not external risk.	ai	2026/07/21
npm-metadata	url-dep:cdk-build-tools	AI (npm-metadata): Monorepo devDependency, internal build tool, not external risk.	ai	2026/07/21
npm-metadata	url-dep:pkglint	AI (npm-metadata): Monorepo devDependency, internal build tool, not external risk.	ai	2026/07/21
source-diff	obfuscated-file:.warnings.jsii.js	AI (source-diff): jsii-generated deprecation warning file, standard for all @aws-cdk/* packages.	ai	2026/07/21
source-diff	obfuscated-file:lib/auto-delete-objects-handler/index.js	AI (source-diff): Standard S3 bucket-empty-on-delete handler, compiled output triggers line-length heuristic.	ai	2026/07/21
source-diff	obfuscated-file:lib/auto-delete-objects-handler/__entrypoint__.js	AI (source-diff): Generated CFN custom-resource framework code, not obfuscation; readable sample confirms.	ai	2026/07/21
source-diff	obfuscated-file-transition:lib/bucket-policy.js	AI (source-diff): Long line is base64 sourcemap comment from tsc compile, standard for CDK build output.	ai	2026/07/21
source-diff	obfuscated-file:test/test.bucket-policy.js	AI (source-diff): Long line is a sourcemap/compiled test artifact, not injected obfuscation; sample shows clean CDK test code.	ai	2026/07/21
publish-pattern	dormant-publish	AI (publish-pattern): Expected cadence for a 288-version monorepo package from a trusted long-running publisher.	ai	2026/07/21
phantom-deps	phantom-dep:constructs	AI (phantom-deps): constructs is a peer/jsii dependency referenced via generated code, not a real phantom import.	ai	2026/07/21
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	2026/04/26
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	2026/04/26

Versions (showing 40 of 240)

Version	Deps	Published
1.31.0	5 / 7	2020-03-24
1.30.0	5 / 7	2020-03-18
1.29.0	5 / 7	2020-03-18
1.28.0	4 / 7	2020-03-16
1.27.0	4 / 7	2020-03-03
1.26.0	4 / 7	2020-02-26
1.25.0	4 / 7	2020-02-19
1.24.0	4 / 7	2020-02-14
1.23.0	4 / 7	2020-02-07
1.22.0	4 / 7	2020-01-23
1.21.1	4 / 7	2020-01-16
1.21.0	4 / 7	2020-01-16
1.20.0	4 / 7	2020-01-07
1.19.0	4 / 5	2019-12-17
1.18.0	4 / 5	2019-11-25
1.17.1	4 / 5	2019-11-19
1.17.0	4 / 5	2019-11-19
1.16.3	4 / 5	2019-11-13
1.16.2	4 / 5	2019-11-12
1.16.1	4 / 5	2019-11-12
1.16.0	4 / 5	2019-11-11
1.15.0	4 / 5	2019-10-28
1.14.0	4 / 5	2019-10-22
1.13.1	4 / 5	2019-10-15
1.13.0	4 / 5	2019-10-15
1.12.0	4 / 5	2019-10-07
1.11.0	4 / 5	2019-10-02
1.10.1	4 / 5	2019-10-01
1.10.0	4 / 5	2019-09-30
1.9.0	4 / 5	2019-09-20
1.8.0	4 / 5	2019-09-10
1.7.0	4 / 5	2019-09-06
1.6.1	4 / 5	2019-08-29
1.6.0	4 / 5	2019-08-27
1.5.0	4 / 5	2019-08-21
1.4.0	4 / 5	2019-08-14
1.3.0	4 / 5	2019-08-02
1.2.0	4 / 5	2019-07-25
1.1.0	4 / 5	2019-07-19
1.0.0	4 / 5	2019-07-11

v1.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.30.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.24.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.21.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.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.

v1.16.3

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.

v1.16.2

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.

v1.16.1

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.

v1.16.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.

v1.15.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.

v1.14.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.

v1.13.1

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.

v1.13.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.

v1.12.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.

v1.11.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.

v1.10.1

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.

v1.10.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.

v1.9.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.

v1.8.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.

v1.7.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.

v1.6.1

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.

v1.6.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.

v1.5.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.

v1.4.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.

v1.3.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.

v1.2.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.

v1.1.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.

v1.0.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.