falafel
transform the ast on a recursive walk
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): Legitimate maintainer transition from substack to goto-bus-stop, a highly trusted publisher with 1237 approved packages and 8+ years of history. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): goto-bus-stop is a well-established maintainer taking over substack's package; this is a known ecosystem pattern. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.2.5 | 2 / 6 | |
| 2.2.4 | 4 / 6 | |
| 2.2.3 | 4 / 5 | |
| 2.2.2 | 4 / 4 | |
| 2.2.1 | 4 / 4 | |
| 2.2.0 | 4 / 4 | |
| 2.1.0 | 4 / 4 | |
| 2.0.0 | 4 / 4 | |
| 1.2.0 | 4 / 3 | |
| 1.1.1 | 4 / 2 | |
| 1.1.0 | 1 / 1 | |
| 1.0.1 | 1 / 1 | |
| 1.0.0 | 1 / 1 | |
| 0.3.1 | 0 / 1 | |
| 0.3.0 | 0 / 1 | |
| 0.2.1 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.6 | 1 / 2 | |
| 0.1.5 | 1 / 2 | |
| 0.1.4 | 1 / 1 | |
| 0.1.3 | 1 / 1 | |
| 0.1.2 | 1 / 1 | |
| 0.1.1 | 1 / 1 | |
| 0.1.0 | 1 / 1 | |
| 0.0.2 | 1 / 1 | |
| 0.0.1 | 1 / 1 | |
| 0.0.0 | 1 / 1 |
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
2 findingsThis version was published by a different npm account than previous versions on 2020-03-09. 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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.