escomplex-plugin-metrics-project MPL-2.0 12 versions

escomplex-plugin-metrics-project

npm Repository Homepage

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

12

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

typhonjsescomplexpluginmetricsproject

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 Mike Leahy, the original author — same person consolidating under their primary npm account. Repository, email, and org all confirm this is a self-transfer, not a hijack.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): typhonrt is the original author's primary npm account; addition is a legitimate self-transfer within the typhonjs org.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): mike leahy and typhonrt are the same person; removal of the secondary account is benign.	ai	2026/04/24

Versions (showing 12 of 12)

Version	Deps	Published
0.1.0	1 / 3	2018-12-21
0.0.13	1 / 3	2016-08-10
0.0.12	1 / 3	2016-08-09
0.0.11	1 / 3	2016-08-08
0.0.10	1 / 3	2016-08-03
0.0.9	1 / 3	2016-08-02
0.0.8	1 / 3	2016-07-25
0.0.6	1 / 3	2016-07-22
0.0.5	1 / 3	2016-07-22
0.0.4	1 / 2	2016-07-06
0.0.2	0 / 2	2016-06-30
0.0.1	0 / 2	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.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.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.