escomplex-ast-moz
Mozilla-format AST walker for escomplex.
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 philbooth to jaredstilwell occurred in 2015; all package metadata (repo, homepage, author) consistently references jared-stilwell. Legitimate project transfer, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers added as part of the same 2015 legitimate project transfer. jaredstilwell has 29 approved packages and 0 rejected. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load local syntax plugin modules by name — a standard extensible plugin pattern for an AST walker. No remote or user-controlled input involved. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.2.1 | 2 / 5 | |
| 0.1.6 | 2 / 4 | |
| 0.1.5 | 2 / 4 | |
| 0.1.4 | 2 / 4 | |
| 0.1.3 | 2 / 4 | |
| 0.1.2 | 2 / 4 | |
| 0.1.1 | 2 / 4 | |
| 0.1.0 | 2 / 4 |
v0.2.1
2 findingsThis version was published by a different npm account than previous versions on 2015-10-20. 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.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.