typhonjs-escomplex-project MPL-2.0 13 versions

typhonjs-escomplex-project

npm Repository Homepage

Provides project oriented AST processing for typhonjs-escomplex complexity reports.

13

Versions

MPL-2.0

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

typhonrt

Keywords

typhonjsescomplexcomplexitysimplicitycyclomatichalsteadmaintainabilitydependenciesstaticanalysismetricses6es6es7es8es9es10

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): typhonrt is the same person as Mike Leahy (GitHub URL in package.json maintainers block points to typhonrt); this is a self-transfer, not a hostile takeover. Stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer typhonrt is the package author operating under a different npm username; legitimate identity confirmed via package.json metadata.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): mike leahy and typhonrt are the same individual; removal of one alias is not a security concern for this package.	ai	2026/04/24

Versions (showing 13 of 13)

Version	Deps	Published
0.1.0	4 / 8	2018-12-21
0.0.12	4 / 7	2016-08-10
0.0.11	4 / 7	2016-08-09
0.0.10	4 / 7	2016-08-09
0.0.9	4 / 7	2016-08-03
0.0.8	4 / 7	2016-08-02
0.0.7	4 / 7	2016-08-02
0.0.6	4 / 7	2016-07-25
0.0.5	4 / 7	2016-07-22
0.0.4	4 / 6	2016-07-06
0.0.3	3 / 6	2016-07-02
0.0.2	3 / 6	2016-06-30
0.0.1	3 / 6	2016-06-13

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.12

1 finding

LOW No provenance attestation provenance

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

v0.0.11

1 finding

LOW No provenance attestation provenance

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

v0.0.10

1 finding

LOW No provenance attestation provenance

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

v0.0.9

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

2 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (mike leahy) were replaced by new maintainers (typhonrt). This is a strong signal of a potential package hijack and requires careful review.

LOW No provenance attestation provenance

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

v0.0.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.