← Home

worker-loader

worker loader module for webpack

34
Versions
MIT
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

evilebottnawisokrajhnnsmichael-ciniawskyd3viant0nebebrawericclemmonstrysoundthelarkinn

Keywords

webpack

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition within webpack-contrib org; evilebottnawi is a known core webpack ecosystem maintainer. ai
maintainer-change maintainer-added AI (maintainer-change): evilebottnawi is a well-established webpack-contrib maintainer; addition is a normal org stewardship change. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous maintainers removed as part of normal webpack-contrib project handoff. ai

Versions (showing 34 of 34)

Version Deps Published
3.0.8 2 / 26
3.0.7 2 / 27
3.0.6 2 / 27
3.0.5 2 / 27
3.0.4 2 / 27
3.0.3 2 / 27
3.0.2 2 / 27
3.0.1 2 / 27
3.0.0 2 / 27
2.0.0 2 / 18
1.1.1 2 / 18
1.1.0 2 / 18
1.0.0 2 / 7
0.8.1 2 / 6
0.8.0 1 / 6
0.7.1 1 / 0
0.7.0 1 / 0
0.6.0 1 / 0
0.5.7 1 / 0
0.5.6 1 / 0
0.5.5 1 / 0
0.5.4 1 / 0
0.5.3 2 / 0
0.5.2 2 / 0
0.5.1 2 / 0
0.5.0 2 / 0
0.2.3 1 / 0
0.2.2 1 / 0
0.2.1 1 / 0
0.2.0 1 / 0
0.1.3 1 / 0
0.1.2 1 / 0
0.1.1 1 / 0
0.1.0 1 / 0

v3.0.8

1 finding
LOW No provenance attestation provenance

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

v3.0.7

1 finding
LOW No provenance attestation provenance

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

v3.0.6

1 finding
LOW No provenance attestation provenance

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

v3.0.5

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v3.0.1

1 finding
LOW No provenance attestation provenance

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

v3.0.0

2 findings
HIGH Publisher changed: shellscape → evilebottnawi (on 2020-08-01) provenance

This version was published by a different npm account than previous versions on 2020-08-01. 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.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: michael-ciniawsky → shellscape (on 2018-05-27) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-05-27. This could indicate a legitimate maintainer transition or an account compromise.