@aws-cdk/aws-ecr-assets
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
awscdkconstructsassetsdocker
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aws-cdk/assets | AI (dependencies): Sibling package in the AWS CDK v1 monorepo, published by the same trusted aws-cdk-team at the same version. No risk. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-s3 | AI (phantom-deps): jsii CDK packages use dependencies via type re-exports and transitive usage; not directly imported does not indicate a phantom dep risk in this monorepo context. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-iam | AI (phantom-deps): Same as aws-s3: jsii CDK monorepo pattern; dependency is legitimately declared and used transitively. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 1.204.0 | 7 / 10 |
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.