← Home

escomplex-ast-moz

Mozilla-format AST walker for escomplex.

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

addisonjjaredstilwellphilbooth

Keywords

escomplexcomplexitysimplicitycyclomatichalsteadmaintainabilitydependenciesstaticanalysismetricsastwalker

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 findings
HIGH Publisher changed: philbooth → jaredstilwell (on 2015-10-20) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.