@cdktf/hcl2cdk
Transform HCL into CDK
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@cdktf/commons | AI (dependencies): Same-org sibling package published in lockstep version. | ai | |
| dependencies | unvetted-dep:@cdktf/provider-schema | AI (dependencies): Same-org sibling package published in lockstep version. | ai | |
| dependencies | unvetted-dep:@cdktf/provider-generator | AI (dependencies): Same-org sibling package published in lockstep version. | ai | |
| phantom-deps | phantom-dep:@cdktf/provider-schema | AI (phantom-deps): Same org scope, false positive. | ai | |
| phantom-deps | phantom-dep:graphology-types | AI (phantom-deps): Type-only dep used in config, not a real concern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.21.0 | 18 / 11 | |
| 0.20.12 | 18 / 11 | |
| 0.20.11 | 18 / 10 | |
| 0.20.10 | 18 / 10 | |
| 0.20.9 | 18 / 10 |
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.