@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, 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:@gershy/util-nodejs-proc | AI (dependencies): Same-namespace dep from a publisher with 104 approved packages; fits IAC use case for process management. | ai | |
| 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 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.0.49 | 5 / 7 | |
| 0.0.48 | 5 / 7 | |
| 0.0.47 | 5 / 7 | |
| 0.0.46 | 5 / 7 | |
| 0.0.45 | 5 / 7 | |
| 0.0.44 | 5 / 6 | |
| 0.0.43 | 5 / 6 | |
| 0.0.42 | 5 / 6 | |
| 0.0.41 | 5 / 6 | |
| 0.0.40 | 5 / 6 | |
| 0.0.39 | 5 / 6 | |
| 0.0.38 | 5 / 6 | |
| 0.0.37 | 5 / 6 | |
| 0.0.36 | 5 / 6 | |
| 0.0.35 | 5 / 6 | |
| 0.0.34 | 5 / 6 | |
| 0.0.33 | 5 / 6 | |
| 0.0.32 | 5 / 6 | |
| 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.18 | 5 / 8 | |
| 0.0.17 | 5 / 8 | |
| 0.0.16 | 5 / 8 | |
| 0.0.15 | 5 / 8 | |
| 0.0.14 | 4 / 8 | |
| 0.0.13 | 6 / 6 | |
| 0.0.12 | 6 / 3 | |
| 0.0.11 | 5 / 3 | |
| 0.0.10 | 4 / 3 | |
| 0.0.9 | 4 / 3 | |
| 0.0.8 | 4 / 3 | |
| 0.0.7 | 4 / 3 | |
| 0.0.6 | 4 / 3 | |
| 0.0.5 | 4 / 3 | |
| 0.0.4 | 4 / 3 | |
| 0.0.3 | 2 / 3 | |
| 0.0.2 | 2 / 3 | |
| 0.0.1 | 2 / 3 |
v0.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.