← Home

@cdktf/cli-core

npm Repository Homepage

CDK for Terraform CLI Core, meant for internal use only

5
Versions
MPL-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

cdktf-teamansgardschmidtnara

Keywords

cdkcdktfterraform

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:env-spread AI (semgrep): Passes env to pipenv install subprocess; normal CLI behavior. ai
semgrep semgrep:dynamic-require AI (semgrep): Loads local cdktf.json config path; stable pattern. ai
semgrep semgrep:child-process-import AI (semgrep): child_process in scaffold hook templates; expected for a CLI. ai
semgrep semgrep:env-bulk-read AI (semgrep): Filters TF_VAR_ keys before synth; benign config read. ai

Versions (showing 5 of 5)

Version Deps Published
0.21.0 49 / 41
0.20.12 49 / 41
0.20.11 49 / 37
0.20.10 49 / 37
0.20.9 49 / 37

v0.21.0

2 findings
HIGH env-spread: src/lib/dependencies/package-manager.js:215 semgrep

Spreading entire process.env into an object — may capture all secrets 213 | await (0, commons_1.exec)("pipenv", ["install", `${packageName}~=${packageVersion}`], { 214 | cwd: this.workingDirectory, > 215 | env: { 216 | ...process.env, 217 | PIPENV_QUIET: "1",

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.20.12

2 findings
HIGH env-spread: src/lib/dependencies/package-manager.js:215 semgrep

Spreading entire process.env into an object — may capture all secrets 213 | await (0, commons_1.exec)("pipenv", ["install", `${packageName}~=${packageVersion}`], { 214 | cwd: this.workingDirectory, > 215 | env: { 216 | ...process.env, 217 | PIPENV_QUIET: "1",

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.20.11

2 findings
HIGH env-spread: src/lib/dependencies/package-manager.js:215 semgrep

Spreading entire process.env into an object — may capture all secrets 213 | await (0, commons_1.exec)("pipenv", ["install", `${packageName}~=${packageVersion}`], { 214 | cwd: this.workingDirectory, > 215 | env: { 216 | ...process.env, 217 | PIPENV_QUIET: "1",

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.20.10

2 findings
HIGH env-spread: src/lib/dependencies/package-manager.js:215 semgrep

Spreading entire process.env into an object — may capture all secrets 213 | await (0, commons_1.exec)("pipenv", ["install", `${packageName}~=${packageVersion}`], { 214 | cwd: this.workingDirectory, > 215 | env: { 216 | ...process.env, 217 | PIPENV_QUIET: "1",

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.20.9

2 findings
HIGH env-spread: src/lib/dependencies/package-manager.js:215 semgrep

Spreading entire process.env into an object — may capture all secrets 213 | await (0, commons_1.exec)("pipenv", ["install", `${packageName}~=${packageVersion}`], { 214 | cwd: this.workingDirectory, > 215 | env: { 216 | ...process.env, 217 | PIPENV_QUIET: "1",

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.