escomplex-plugin-syntax-babylon MPL-2.0 13 versions

escomplex-plugin-syntax-babylon

npm Repository Homepage

Provides a plugin for typhonjs-escomplex module processing which loads syntax definitions for trait resolution for Babylon AST.

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

typhonjsescomplexpluginsyntaxdefinitionsbabelparser

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 typhonjs ecosystem author; the repo URL and maintainer email already pointed to typhonjs/typhonrt before this version. Legitimate consolidation, not a hijack.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): typhonrt is the established owner of the typhonjs ecosystem with 158 approved packages; addition is a legitimate transfer.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Mike Leahy and typhonrt are the same person/org; removal reflects account consolidation, not a hostile takeover.	ai	2026/04/24

Versions (showing 13 of 13)

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

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.