typhonjs-escomplex-commons MPL-2.0 18 versions

typhonjs-escomplex-commons

npm Repository Homepage

Provides core common utilities for typhonjs-escomplex modules and plugins.

18

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

typhonjsescomplexcommonsreporttraitsformats

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 original author (Mike Leahy) operating under their primary npm account; the typhonjs brand and typhonrt account are the same entity. Not a hostile takeover.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): typhonrt is the package's original author/brand owner; addition is a legitimate account consolidation.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): mike leahy and typhonrt are the same person; removal reflects account consolidation, not a hostile takeover.	ai	2026/04/24

Versions (showing 18 of 18)

Version	Deps	Published
0.1.1	0 / 3	2019-01-10
0.1.0	0 / 3	2018-12-21
0.0.16	0 / 3	2016-08-09
0.0.15	0 / 3	2016-08-08
0.0.14	0 / 3	2016-08-03
0.0.13	0 / 3	2016-08-02
0.0.12	0 / 3	2016-07-24
0.0.11	0 / 3	2016-07-22
0.0.10	0 / 3	2016-07-22
0.0.9	0 / 3	2016-07-22
0.0.8	0 / 2	2016-07-06
0.0.7	0 / 2	2016-07-02
0.0.6	0 / 2	2016-07-02
0.0.5	0 / 2	2016-06-30
0.0.4	0 / 2	2016-06-30
0.0.3	0 / 2	2016-06-30
0.0.2	0 / 2	2016-06-30
0.0.1	0 / 2	2016-06-13

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.16

1 finding

LOW No provenance attestation provenance

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

v0.0.15

1 finding

LOW No provenance attestation provenance

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

v0.0.14

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