@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 53 of 153)
| Version | Deps | Published |
|---|---|---|
| 1.39.0 | 5 / 7 | |
| 1.38.0 | 5 / 7 | |
| 1.37.0 | 5 / 7 | |
| 1.36.1 | 4 / 7 | |
| 1.36.0 | 4 / 7 | |
| 1.35.0 | 4 / 7 | |
| 1.34.1 | 4 / 7 | |
| 1.34.0 | 4 / 7 | |
| 1.33.1 | 4 / 7 | |
| 1.33.0 | 4 / 7 | |
| 1.32.2 | 4 / 7 | |
| 1.32.1 | 4 / 7 | |
| 1.32.0 | 4 / 7 | |
| 1.31.0 | 4 / 7 | |
| 1.30.0 | 4 / 7 | |
| 1.29.0 | 4 / 7 | |
| 1.28.0 | 3 / 7 | |
| 1.27.0 | 3 / 7 | |
| 1.26.0 | 3 / 7 | |
| 1.25.0 | 3 / 7 | |
| 1.24.0 | 3 / 7 | |
| 1.23.0 | 3 / 7 | |
| 1.22.0 | 3 / 7 | |
| 1.21.1 | 3 / 7 | |
| 1.21.0 | 3 / 7 | |
| 1.20.0 | 3 / 7 | |
| 1.19.0 | 3 / 5 | |
| 1.18.0 | 3 / 5 | |
| 1.17.1 | 3 / 5 | |
| 1.17.0 | 3 / 5 | |
| 1.16.3 | 3 / 5 | |
| 1.16.2 | 3 / 5 | |
| 1.16.1 | 3 / 5 | |
| 1.16.0 | 3 / 5 | |
| 1.15.0 | 3 / 5 | |
| 1.14.0 | 3 / 5 | |
| 1.13.1 | 3 / 5 | |
| 1.13.0 | 3 / 5 | |
| 1.12.0 | 3 / 5 | |
| 1.11.0 | 3 / 5 | |
| 1.10.1 | 3 / 5 | |
| 1.10.0 | 3 / 5 | |
| 1.9.0 | 3 / 5 | |
| 1.8.0 | 3 / 5 | |
| 1.7.0 | 3 / 5 | |
| 1.6.1 | 3 / 5 | |
| 1.6.0 | 3 / 5 | |
| 1.5.0 | 3 / 5 | |
| 1.4.0 | 3 / 5 | |
| 1.3.0 | 3 / 5 | |
| 1.2.0 | 3 / 5 | |
| 1.1.0 | 3 / 5 | |
| 1.0.0 | 3 / 5 |
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.