typhonjs-plugin-manager MPL-2.0 19 versions

typhonjs-plugin-manager

npm Repository Homepage

Provides a plugin manager that dispatches events to loaded plugins.

19

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

typhonjspluginmanager

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 package author (Mike Leahy) operating under their npm handle; same GitHub URL in package.json, 160 approved packages, no hostile takeover evidence.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainer typhonrt is the same person as the original author Mike Leahy; consistent identity across package.json and npm profile.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): mike leahy and typhonrt are the same person; display name change, not a real removal of a distinct maintainer.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is the core intended functionality of a plugin manager — it loads plugins by path. The code validates the path before loading. This is a stable false positive for this package.	ai	2026/04/23

Versions (showing 19 of 19)

Version	Deps	Published
0.2.0	3 / 2	2017-08-25
0.1.11	2 / 2	2017-07-14
0.1.10	2 / 2	2017-07-14
0.1.9	2 / 2	2017-05-31
0.1.8	2 / 2	2017-03-30
0.1.7	2 / 2	2017-03-10
0.1.6	2 / 2	2017-03-10
0.1.5	2 / 2	2017-03-08
0.1.4	2 / 2	2017-02-27
0.1.3	2 / 2	2017-02-27
0.1.2	2 / 2	2017-02-21
0.1.1	2 / 2	2017-02-14
0.1.0	1 / 2	2017-02-12
0.0.6	1 / 2	2017-01-28
0.0.5	1 / 2	2017-01-28
0.0.4	1 / 2	2017-01-10
0.0.3	0 / 2	2016-07-06
0.0.2	0 / 2	2016-07-06
0.0.1	0 / 2	2016-06-13

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

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