← Home

escomplex-traits

Traits for escomplex AST walkers.

5
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

escomplexcomplexitysimplicitycyclomatichalsteadmaintainabilitydependenciesstaticanalysismetricstraits

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change occurred in 2015; new publisher jaredstilwell has 29 approved packages, repo URL matches new maintainer identity — legitimate historical transition. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer addition is a 2015 event consistent with a legitimate project transfer; no malicious signals in any subsequent versions. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy preceded the 2015 publish; package has been stable for years since with approved dependents and no issues. ai

Versions (showing 5 of 5)

Version Deps Published
0.3.0 0 / 5
0.2.0 0 / 5
0.1.2 0 / 5
0.1.1 0 / 5
0.1.0 0 / 3

v0.3.0

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.2.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.