static-module
convert module usage to inline 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): Known legitimate transfer from substack to goto-bus-stop, a trusted maintainer with strong track record. Common pattern for substack's packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Bulk maintainer addition is part of substack's known package transfer pattern to trusted community maintainers. | ai | |
| provenance | no-provenance | AI (provenance): Package published in 2017, before Sigstore provenance existed. Expected for this era. | ai | |
| source-diff | obfuscated-file:bench/input.js | AI (source-diff): bench/input.js is a bundled copy of acorn (JS parser) used as benchmark input, not obfuscated malicious code. Stable false positive for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 14 / 7 | |
| 3.0.3 | 14 / 7 | |
| 3.0.2 | 14 / 7 | |
| 3.0.1 | 14 / 7 | |
| 3.0.0 | 14 / 7 | |
| 2.2.5 | 14 / 5 | |
| 2.2.4 | 14 / 5 | |
| 2.2.3 | 14 / 5 | |
| 2.2.2 | 14 / 5 | |
| 2.2.1 | 14 / 5 | |
| 2.2.0 | 14 / 4 | |
| 2.1.1 | 11 / 2 | |
| 2.1.0 | 11 / 2 | |
| 2.0.0 | 11 / 2 | |
| 1.5.0 | 11 / 2 | |
| 1.4.0 | 11 / 2 | |
| 1.3.2 | 11 / 2 | |
| 1.3.1 | 11 / 2 | |
| 1.3.0 | 11 / 2 | |
| 1.2.0 | 11 / 2 | |
| 1.1.3 | 11 / 2 | |
| 1.1.2 | 11 / 1 | |
| 1.1.1 | 11 / 1 | |
| 1.1.0 | 11 / 1 | |
| 1.0.1 | 10 / 1 | |
| 1.0.0 | 10 / 1 | |
| 0.0.9 | 10 / 1 | |
| 0.0.7 | 10 / 1 | |
| 0.0.6 | 10 / 1 | |
| 0.0.5 | 10 / 1 | |
| 0.0.4 | 10 / 1 | |
| 0.0.3 | 10 / 1 | |
| 0.0.2 | 10 / 1 | |
| 0.0.1 | 10 / 1 | |
| 0.0.0 | 10 / 1 |
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
2 findingsThis version was published by a different npm account than previous versions on 2017-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.