autoevals
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Consistent across all 123 versions; no provenance is the norm for this publisher. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in numeric transform helper to compile user-supplied math expressions; not a code-injection risk in this context. | ai | |
| phantom-deps | phantom-dep:linear-sum-assignment | AI (phantom-deps): Declared runtime dep used internally; phantom-dep heuristic fires because it's not directly imported at top level. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.0.132 | 9 / 12 | |
| 0.0.131 | 9 / 12 | |
| 0.0.130 | 9 / 12 | |
| 0.0.129 | 10 / 12 |
v0.0.132
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.131
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.130
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.129
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.