escomplex
Software complexity analysis of JavaScript-family abstract syntax trees.
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 addisonj occurred in Feb 2015 (~10 years ago). addisonj has 98 approved packages and a clean track record; this is a long-established legitimate maintainer transition. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): addisonj was added as maintainer in 2015 and has a strong track record (98 approved, 0 rejected). Transition is historical and well-established. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 2 / 5 | |
| 1.2.0 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.0 | 2 / 5 | |
| 0.2.6 | 2 / 5 | |
| 0.2.5 | 2 / 6 | |
| 0.2.4 | 2 / 6 | |
| 0.2.3 | 2 / 6 | |
| 0.2.2 | 2 / 6 | |
| 0.2.1 | 2 / 6 | |
| 0.2.0 | 2 / 6 | |
| 0.1.3 | 1 / 6 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 | |
| 2.0.0-alpha | 1 / 7 |
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2015-10-21. 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.
v1.2.0
2 findingsThis version was published by a different npm account than previous versions on 2015-03-02. 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.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2015-02-23. 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.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.