escomplex-plugin-metrics-module MPL-2.0 13 versions

escomplex-plugin-metrics-module

npm Repository Homepage

Provides the core module metric / report generation plugin for typhonjs-escomplex module processing.

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

typhonjsescomplexpluginmetricsmodule

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 TyphonJS org maintainer (157 approved packages, 3611 days history); the repo, email, and GitHub URL all point to the same org. This is a legitimate consolidation under the org's npm handle.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): typhonrt is the established TyphonJS publisher; addition is consistent with org ownership of this package.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): mike leahy and typhonrt are the same individual/org; removal is part of a legitimate account consolidation.	ai	2026/04/24

Versions (showing 13 of 13)

Version	Deps	Published
0.1.0	1 / 4	2018-12-21
0.0.13	1 / 4	2016-08-10
0.0.12	1 / 4	2016-08-09
0.0.11	1 / 4	2016-08-08
0.0.10	1 / 4	2016-08-03
0.0.9	1 / 4	2016-08-02
0.0.8	1 / 4	2016-07-24
0.0.7	1 / 4	2016-07-22
0.0.6	1 / 4	2016-07-22
0.0.4	1 / 4	2016-07-06
0.0.3	1 / 4	2016-07-02
0.0.2	1 / 4	2016-06-30
0.0.1	1 / 4	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.13

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

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