@aws-cdk/aws-ecr
Supply chain provenance
Status for the latest visible version.
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
Keywords
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-local build tool reference, standard for aws-cdk packages. | ai | |
| npm-metadata | url-dep:pkglint | AI (npm-metadata): Monorepo-local build tool reference, standard for aws-cdk packages. | ai | |
| npm-metadata | url-dep:cdk-build-tools | AI (npm-metadata): Monorepo-local build tool reference, standard for aws-cdk packages. | ai | |
| npm-metadata | url-dep:cdk-integ-tools | AI (npm-metadata): Monorepo-local build tool reference, standard for aws-cdk packages. | ai | |
| source-diff | obfuscated-file:test/cdk.out/asset.a75563f489fb6bc4064bc85b91ef607f671326e647bcd9d9bcab0731de62edd4/index.js | AI (source-diff): Bundled test fixture (custom-resource handler), not obfuscated malicious code. | ai | |
| phantom-deps | phantom-dep:constructs | AI (phantom-deps): jsii construct lib; constructs used indirectly via generated code. | ai |
Versions (showing 51 of 153)
| Version | Deps | Published |
|---|---|---|
| 1.204.0 | 5 / 6 | |
| 1.203.0 | 5 / 6 | |
| 1.202.0 | 5 / 6 | |
| 1.201.0 | 5 / 6 | |
| 1.200.0 | 5 / 6 | |
| 1.199.0 | 5 / 6 | |
| 1.198.1 | 5 / 6 | |
| 1.198.0 | 5 / 6 | |
| 1.197.0 | 5 / 6 | |
| 1.196.0 | 5 / 6 | |
| 1.195.0 | 5 / 6 | |
| 1.194.0 | 5 / 6 | |
| 1.193.0 | 5 / 6 | |
| 1.192.0 | 5 / 6 | |
| 1.191.0 | 5 / 6 | |
| 1.190.0 | 5 / 6 | |
| 1.189.0 | 5 / 6 | |
| 1.188.0 | 5 / 6 | |
| 1.187.0 | 5 / 6 | |
| 1.186.1 | 5 / 6 | |
| 1.186.0 | 5 / 6 | |
| 1.185.0 | 5 / 6 | |
| 1.184.1 | 5 / 6 | |
| 1.184.0 | 5 / 6 | |
| 1.183.0 | 5 / 6 | |
| 1.182.0 | 5 / 6 | |
| 1.181.1 | 5 / 6 | |
| 1.181.0 | 5 / 6 | |
| 1.180.0 | 5 / 6 | |
| 1.179.0 | 5 / 6 | |
| 1.178.0 | 5 / 6 | |
| 1.177.0 | 5 / 6 | |
| 1.176.0 | 5 / 6 | |
| 1.175.0 | 5 / 6 | |
| 1.174.0 | 5 / 6 | |
| 1.173.0 | 5 / 6 | |
| 1.172.0 | 5 / 6 | |
| 1.171.0 | 5 / 6 | |
| 1.170.1 | 5 / 6 | |
| 1.170.0 | 5 / 6 | |
| 1.169.0 | 5 / 6 | |
| 1.168.0 | 5 / 6 | |
| 1.167.0 | 5 / 6 | |
| 1.166.1 | 5 / 6 | |
| 1.165.0 | 5 / 6 | |
| 1.164.0 | 5 / 6 | |
| 1.87.1 | 4 / 7 | |
| 1.87.0 | 4 / 7 | |
| 1.86.0 | 4 / 7 | |
| 1.85.0 | 4 / 7 | |
| 1.84.0 | 4 / 7 |
v1.203.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.202.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.201.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.200.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.199.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.198.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.198.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.197.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.196.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.195.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.194.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.193.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.192.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.191.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.190.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.189.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.188.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.187.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.186.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.186.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.185.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.184.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.184.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.183.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.182.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.181.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.181.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.180.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.179.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.178.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.177.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.176.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.175.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.174.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.173.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.172.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.171.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.170.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.170.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.169.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.168.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.167.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.166.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.165.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.164.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.