@ordergroove/smi-precompile
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() used in test helper to execute precompiled template strings — documented, intentional pattern for this precompiler package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in loader.js resolves a user-supplied settings path — expected behavior for a build/precompile tool. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Babel packages loaded by convention in build tooling; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/standalone | AI (phantom-deps): Babel packages loaded by convention in build tooling; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.12.9 | 9 / 1 | |
| 1.12.8 | 12 / 1 | |
| 1.12.7 | 12 / 1 | |
| 1.12.6 | 12 / 1 | |
| 1.12.5 | 12 / 1 | |
| 1.12.4 | 12 / 1 | |
| 1.12.3 | 12 / 1 | |
| 1.12.2 | 12 / 1 | |
| 1.12.1 | 12 / 1 | |
| 1.12.0 | 12 / 1 |
v1.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.