← Home

load-plugins

npm Repository Homepage
8
Versions
—
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

jaridmargolinjonschlinkerttrysound

Keywords

depdepsglobgruntgulphelperhelpersloadloadermatchmatchdepmiddlewareminimatchmodulemodulestaskpluginpluginsresolveresolved

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change occurred in 2016 (~9 years ago) as a legitimate maintainer transition from trysound to jaridmargolin; no subsequent issues observed. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer addition of jaridmargolin in 2016 is a historical, legitimate transition; stable for this package. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy gap aligns with the 2016 maintainer transition; no malicious activity detected then or since. ai
semgrep semgrep:dynamic-require AI (semgrep): Dynamic require is the core mechanism of a plugin loader — resolving and requiring plugins by path is the package's documented purpose, not a security risk. ai

Versions (showing 8 of 8)

Version Deps Published
2.1.2 3 / 7
2.1.1 3 / 7
2.1.0 3 / 7
2.0.1 3 / 7
2.0.0 4 / 7
1.0.2 3 / 7
1.0.1 3 / 7
1.0.0 3 / 7

v2.1.2

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.

v2.1.1

2 findings
HIGH Publisher changed: trysound → jaridmargolin (on 2016-09-21) provenance

This version was published by a different npm account than previous versions on 2016-09-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.1.0

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.

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

v2.0.0

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.

v1.0.2

1 finding
LOW No provenance attestation provenance

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

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

v1.0.0

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.