@aws-cdk/aws-s3-assets No license 42 versions

@aws-cdk/aws-s3-assets

npm Repository Homepage

42

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

awscdks3constructsassets

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	url-dep:cdk-integ-tools	AI (npm-metadata): Monorepo-local dev tool reference, standard for aws-cdk packages.	ai	2026/07/21
npm-metadata	url-dep:cdk-build-tools	AI (npm-metadata): Monorepo-local dev tool reference, standard for aws-cdk packages.	ai	2026/07/21
npm-metadata	url-dep:pkglint	AI (npm-metadata): Monorepo-local dev tool reference, standard for aws-cdk packages.	ai	2026/07/21
publish-pattern	new-deps-added	AI (publish-pattern): New dep is official @aws-cdk/aws-kms sibling package.	ai	2026/07/21
publish-pattern	dormant-publish	AI (publish-pattern): Normal monorepo release cadence for aws-cdk-team, not a takeover indicator.	ai	2026/07/21
source-diff	obfuscated-file:test/asset.test.js	AI (source-diff): Long lines are generated asset-hash literals in a test file, not obfuscated code.	ai	2026/07/21
phantom-deps	phantom-dep:constructs	AI (phantom-deps): constructs is a peer dep used indirectly via CDK core; stable false positive.	ai	2026/07/21
dependencies	unvetted-dep:@aws-cdk/assets	AI (dependencies): Sibling AWS CDK v1 package from the same official monorepo release; unvetted status is a systemic artifact, not a security concern.	ai	2026/04/26
dependencies	unvetted-dep:@aws-cdk/aws-kms	AI (dependencies): Sibling AWS CDK v1 package from the same official monorepo release; unvetted status is a systemic artifact, not a security concern.	ai	2026/04/26
dependencies	unvetted-dep:@aws-cdk/aws-iam	AI (dependencies): Sibling AWS CDK v1 package from the same official monorepo release; unvetted status is a systemic artifact, not a security concern.	ai	2026/04/26
dependencies	unvetted-dep:@aws-cdk/aws-s3	AI (dependencies): Sibling AWS CDK v1 package from the same official monorepo release; unvetted status is a systemic artifact, not a security concern.	ai	2026/04/26
dependencies	unvetted-dep:@aws-cdk/core	AI (dependencies): Sibling AWS CDK v1 package from the same official monorepo release; unvetted status is a systemic artifact, not a security concern.	ai	2026/04/26

Versions (showing 42 of 242)

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

v1.32.1

1 finding

LOW No provenance attestation provenance

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

v1.32.0

1 finding

LOW No provenance attestation provenance

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

v1.31.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.30.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.29.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.28.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.27.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.26.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.25.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.24.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.23.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.22.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.21.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.21.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.20.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.19.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.18.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.17.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.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.