@gershy/lilac
Luscious infrastructure Living as Code - an opinionated approach to IAC
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm); no other risk signals present for this package. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): env spread is used to pass host env to Terraform subprocess — standard IaC pattern, not exfiltration. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.31 | 5 / 6 | |
| 0.0.30 | 5 / 6 | |
| 0.0.29 | 5 / 6 | |
| 0.0.28 | 5 / 6 | |
| 0.0.27 | 5 / 6 | |
| 0.0.26 | 5 / 6 | |
| 0.0.23 | 5 / 6 | |
| 0.0.22 | 5 / 9 | |
| 0.0.17 | 5 / 8 | |
| 0.0.14 | 4 / 8 | |
| 0.0.7 | 4 / 3 | |
| 0.0.3 | 2 / 3 |
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
5 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/968289904fd1d3c1482a7ce37ef8c9c8ea8f3f61/cmp/cjs/main.js#L116 114 | this.tfProcArgs = { 115 | timeoutMs: 0, > 116 | env: { 117 | ...process.env, 118 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/968289904fd1d3c1482a7ce37ef8c9c8ea8f3f61/cmp/cjs/util/procTerraform.js#L48 46 | ...opts, 47 | cwd: fact, > 48 | env: { 49 | ...process.env, 50 | TF_DATA_DIR: "",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/968289904fd1d3c1482a7ce37ef8c9c8ea8f3f61/cmp/esm/main.js#L78 76 | this.tfProcArgs = { 77 | timeoutMs: 0, > 78 | env: { 79 | ...process.env, 80 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/968289904fd1d3c1482a7ce37ef8c9c8ea8f3f61/cmp/esm/util/procTerraform.js#L15 13 | ...opts, 14 | cwd: fact, > 15 | env: { 16 | ...process.env, 17 | TF_DATA_DIR: "",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.27
5 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/e585d6b7efac6329121476f209940b38c96ab480/cmp/cjs/main.js#L116 114 | this.tfProcArgs = { 115 | timeoutMs: 0, > 116 | env: { 117 | ...process.env, 118 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/e585d6b7efac6329121476f209940b38c96ab480/cmp/cjs/util/procTerraform.js#L48 46 | ...opts, 47 | cwd: fact, > 48 | env: { 49 | ...process.env, 50 | TF_DATA_DIR: "",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/e585d6b7efac6329121476f209940b38c96ab480/cmp/esm/main.js#L78 76 | this.tfProcArgs = { 77 | timeoutMs: 0, > 78 | env: { 79 | ...process.env, 80 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/e585d6b7efac6329121476f209940b38c96ab480/cmp/esm/util/procTerraform.js#L15 13 | ...opts, 14 | cwd: fact, > 15 | env: { 16 | ...process.env, 17 | TF_DATA_DIR: "",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.26
5 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/50d1f70a51ad277553a35a17854e4da008447c87/cmp/cjs/main.js#L116 114 | this.tfProcArgs = { 115 | timeoutMs: 0, > 116 | env: { 117 | ...process.env, 118 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/50d1f70a51ad277553a35a17854e4da008447c87/cmp/cjs/util/procTerraform.js#L48 46 | ...opts, 47 | cwd: fact, > 48 | env: { 49 | ...process.env, 50 | TF_DATA_DIR: "",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/50d1f70a51ad277553a35a17854e4da008447c87/cmp/esm/main.js#L78 76 | this.tfProcArgs = { 77 | timeoutMs: 0, > 78 | env: { 79 | ...process.env, 80 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/50d1f70a51ad277553a35a17854e4da008447c87/cmp/esm/util/procTerraform.js#L15 13 | ...opts, 14 | cwd: fact, > 15 | env: { 16 | ...process.env, 17 | TF_DATA_DIR: "",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.23
5 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/05a68abb8da4b9401669bce281239cb6d783b4ac/cmp/cjs/main.js#L116 114 | this.tfProcArgs = { 115 | timeoutMs: 0, > 116 | env: { 117 | ...process.env, 118 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/05a68abb8da4b9401669bce281239cb6d783b4ac/cmp/cjs/util/procTerraform.js#L48 46 | ...opts, 47 | cwd: fact, > 48 | env: { 49 | ...process.env, 50 | TF_DATA_DIR: "",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/05a68abb8da4b9401669bce281239cb6d783b4ac/cmp/esm/main.js#L78 76 | this.tfProcArgs = { 77 | timeoutMs: 0, > 78 | env: { 79 | ...process.env, 80 | TF_LOG: "DEBUG",
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/05a68abb8da4b9401669bce281239cb6d783b4ac/cmp/esm/util/procTerraform.js#L15 13 | ...opts, 14 | cwd: fact, > 15 | env: { 16 | ...process.env, 17 | TF_DATA_DIR: "",
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.17
5 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/3638fc8446fd5b657101c0db1e303c5e36ac46e0/cmp/cjs/main.js#L105 103 | this.tfProcArgs = { 104 | timeoutMs: 0, > 105 | env: { 106 | ...process.env, 107 | TF_LOG: 'DEBUG',
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/3638fc8446fd5b657101c0db1e303c5e36ac46e0/cmp/cjs/util/procTerraform.js#L20 18 | ...opts, 19 | cwd: fact, > 20 | env: { 21 | ...process.env, 22 | TF_DATA_DIR: '',
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/3638fc8446fd5b657101c0db1e303c5e36ac46e0/cmp/mjs/main.js#L83 81 | this.tfProcArgs = { 82 | timeoutMs: 0, > 83 | env: { 84 | ...process.env, 85 | TF_LOG: 'DEBUG',
Spreading entire process.env into an object — may capture all secrets Source: https://github.com/gershy/lilac/blob/3638fc8446fd5b657101c0db1e303c5e36ac46e0/cmp/mjs/util/procTerraform.js#L15 13 | ...opts, 14 | cwd: fact, > 15 | env: { 16 | ...process.env, 17 | TF_DATA_DIR: '',
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.