@aws-cdk/aws-cloudformation
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-internal build tool, standard AWS CDK workspace pattern. | ai | |
| npm-metadata | url-dep:pkglint | AI (npm-metadata): Monorepo-internal lint tool, standard AWS CDK workspace pattern. | ai | |
| npm-metadata | url-dep:cdk-build-tools | AI (npm-metadata): Monorepo-internal build tool, standard AWS CDK workspace pattern. | ai | |
| npm-metadata | url-dep:cdk-integ-tools | AI (npm-metadata): Monorepo-internal build tool, standard AWS CDK workspace pattern. | ai | |
| dependencies | unvetted-dep:@aws-cdk/aws-lambda | AI (dependencies): First-party sibling package from the same AWS CDK monorepo and publisher (aws-cdk-team); pinned to the exact same version. No real risk. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-iam | AI (phantom-deps): Same-org CDK sibling package; phantom detection is a false positive due to jsii/re-export patterns common in CDK monorepo packages. | ai | |
| phantom-deps | phantom-dep:constructs | AI (phantom-deps): Standard CDK v1 peer/runtime dependency declared in package.json; phantom detection is a false positive due to jsii/re-export patterns in CDK packages. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/aws-s3 | AI (phantom-deps): Same-org CDK sibling package; phantom detection is a false positive due to jsii/re-export patterns common in CDK monorepo packages. | ai | |
| phantom-deps | phantom-dep:@aws-cdk/cx-api | AI (phantom-deps): Same-org CDK sibling package; phantom detection is a false positive due to jsii/re-export patterns common in CDK monorepo packages. | ai |
Versions (showing 71 of 171)
| Version | Deps | Published |
|---|---|---|
| 1.115.0 | 7 / 13 | |
| 1.114.0 | 7 / 13 | |
| 1.113.0 | 7 / 13 | |
| 1.112.0 | 7 / 13 | |
| 1.111.0 | 7 / 13 | |
| 1.110.1 | 7 / 13 | |
| 1.110.0 | 7 / 13 | |
| 1.109.0 | 7 / 13 | |
| 1.108.1 | 7 / 13 | |
| 1.108.0 | 7 / 13 | |
| 1.107.0 | 7 / 13 | |
| 1.106.1 | 7 / 13 | |
| 1.106.0 | 7 / 13 | |
| 1.105.0 | 7 / 13 | |
| 1.104.0 | 7 / 13 | |
| 1.103.0 | 7 / 13 | |
| 1.102.0 | 7 / 13 | |
| 1.101.0 | 7 / 13 | |
| 1.100.0 | 7 / 13 | |
| 1.99.0 | 7 / 13 | |
| 1.98.0 | 7 / 13 | |
| 1.97.0 | 7 / 13 | |
| 1.96.0 | 7 / 13 | |
| 1.95.2 | 7 / 13 | |
| 1.95.1 | 7 / 13 | |
| 1.95.0 | 7 / 13 | |
| 1.94.1 | 7 / 13 | |
| 1.94.0 | 7 / 13 | |
| 1.93.0 | 7 / 13 | |
| 1.92.0 | 7 / 13 | |
| 1.91.0 | 7 / 13 | |
| 1.90.1 | 7 / 13 | |
| 1.90.0 | 7 / 13 | |
| 1.89.0 | 7 / 13 | |
| 1.88.0 | 7 / 13 | |
| 1.87.1 | 7 / 13 | |
| 1.87.0 | 7 / 13 | |
| 1.86.0 | 7 / 13 | |
| 1.85.0 | 7 / 13 | |
| 1.84.0 | 7 / 13 | |
| 1.83.0 | 7 / 13 | |
| 1.82.0 | 7 / 13 | |
| 1.81.0 | 7 / 13 | |
| 1.80.0 | 7 / 13 | |
| 1.79.0 | 7 / 13 | |
| 1.78.0 | 7 / 13 | |
| 1.77.0 | 7 / 13 | |
| 1.76.0 | 7 / 13 | |
| 1.75.0 | 7 / 13 | |
| 1.74.0 | 7 / 13 | |
| 1.73.0 | 7 / 13 | |
| 1.72.0 | 7 / 13 | |
| 1.71.0 | 7 / 13 | |
| 1.70.0 | 7 / 13 | |
| 1.69.0 | 7 / 13 | |
| 1.68.0 | 7 / 13 | |
| 1.67.0 | 7 / 13 | |
| 1.18.0 | 6 / 11 | |
| 1.17.1 | 6 / 11 | |
| 1.17.0 | 6 / 11 | |
| 1.16.3 | 6 / 11 | |
| 1.16.2 | 6 / 11 | |
| 1.16.1 | 6 / 11 | |
| 1.16.0 | 6 / 11 | |
| 1.15.0 | 6 / 11 | |
| 1.14.0 | 6 / 11 | |
| 1.13.1 | 6 / 11 | |
| 1.13.0 | 6 / 11 | |
| 1.4.0 | 4 / 8 | |
| 1.2.0 | 4 / 8 | |
| 1.0.0 | 4 / 8 |
v1.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.113.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.112.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.110.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.110.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.109.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.106.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.103.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.102.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.101.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.100.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.99.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.98.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.96.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.95.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.90.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.89.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v1.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.67.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. Consider requesting the maintainer enable provenance via CI/CD.
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.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.