static-eval
evaluate statically-analyzable expressions
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 | publisher-changed | AI (provenance): Publisher change from substack to goto-bus-stop occurred in 2019 as part of a well-known legitimate community transfer. goto-bus-stop has an excellent npm track record (1239 approved packages). | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Large maintainer list addition is consistent with a community/org-level transfer in 2019. No malicious indicators; goto-bus-stop is a trusted publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): The spam-flagged maintainer (jmm) is not in the current maintainer list; active publisher goto-bus-stop has a strong clean track record. Signal is historical noise for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 2.1.1 | 1 / 2 | |
| 2.1.0 | 1 / 2 | |
| 2.0.5 | 1 / 2 | |
| 2.0.4 | 1 / 2 | |
| 2.0.3 | 1 / 2 | |
| 2.0.2 | 1 / 2 | |
| 0.2.4 | 1 / 2 | |
| 0.2.3 | 1 / 2 | |
| 0.2.2 | 1 / 2 | |
| 0.2.1 | 1 / 2 | |
| 0.2.0 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 2 | |
| 0.0.0 | 0 / 2 |
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
2 findingsThis version was published by a different npm account than previous versions on 2019-11-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2019-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.