← Home

@cdktn/hcl2json

npm Repository Homepage

Transform HCL into JSON

7
Versions
MPL-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

cdktn-teamjsteinichso0k

Keywords

cdkcdktfcdktnterraformhcl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; this is the documented open-constructs org pattern. ai
maintainer-change maintainer-added AI (maintainer-change): jsteinich is part of the open-constructs org; addition consistent with legitimate team growth. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() is in standard Go wasm_exec.js runtime bridge; expected for WASM-based packages. ai

Versions (showing 7 of 7)

Version Deps Published
0.23.3 1 / 3
0.23.2 1 / 3
0.23.1 1 / 6
0.23.0 1 / 6
0.22.1 1 / 6
0.22.0 1 / 6
0.21.0 1 / 6

v0.23.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.23.2

2 findings
HIGH Publisher changed: cdktn-team → GitHub Actions (on 2026-05-26) provenance

This version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.23.1

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.

v0.23.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.

v0.22.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.

v0.21.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.