← Home

escomplex-js

Javascript wrapping library for escomplex.

9
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

philboothaddisonj

Keywords

escomplexcomplexitysimplicitycyclomatichalsteadmaintainabilitydependenciesstaticanalysismetricsesprima

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change philbooth→addisonj occurred in 2015 (~10 years ago). addisonj has 93 approved packages, 0 rejected, and a long history. Legitimate historical transition, not a recent compromise signal. ai
maintainer-change maintainer-added AI (maintainer-change): Same historical maintainer transition from 2015. addisonj is a well-established publisher with strong track record. Stable false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
1.2.0 4 / 5
1.1.0 4 / 5
1.0.0 4 / 5
0.1.5 4 / 5
0.1.4 4 / 5
0.1.3 4 / 5
0.1.2 4 / 5
0.1.1 4 / 5
0.1.0 4 / 5

v1.2.0

2 findings
HIGH Publisher changed: philbooth → addisonj (on 2015-03-02) provenance

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

LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.0

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.