file-loader MIT 49 versions

file-loader

npm Repository Homepage

A file loader module for webpack

49

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

d3viant0neevilebottnawisokrajhnnsmichael-ciniawskyericclemmonsthelarkinn

Keywords

webpack

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change sokra→d3viant0ne reflects a documented webpack org maintainer expansion in 2017; repo remains under github.com/webpack and all new maintainers are known webpack contributors.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers (bebraw, d3viant0ne, ericclemmons, jhnns, thelarkinn) are recognized webpack ecosystem contributors; this is a legitimate team expansion, not a takeover.	ai	2026/04/22
provenance	no-provenance	AI (provenance): file-loader is a 2000+ day old established webpack-contrib package; lack of Sigstore provenance is expected for packages of this age and is not a risk signal here.	ai	2026/04/21
dependencies	unvetted-dep:loader-utils	AI (dependencies): loader-utils is a core webpack ecosystem utility maintained by webpack-contrib; flagging it as unvetted is a false positive for this package.	ai	2026/04/21

Versions (showing 49 of 49)

Version	Deps	Published
6.2.0	2 / 23	2020-10-27
6.1.1	2 / 23	2020-10-09
6.1.0	2 / 23	2020-08-31
6.0.0	2 / 26	2020-03-17
5.1.0	2 / 26	2020-02-19
5.0.2	2 / 26	2019-11-25
5.0.1	2 / 26	2019-11-25
5.0.0	2 / 26	2019-11-25
4.3.0	2 / 25	2019-11-21
4.2.0	2 / 25	2019-08-07
4.1.0	2 / 25	2019-07-18
4.0.0	2 / 25	2019-06-05
3.0.1	2 / 24	2018-12-20
3.0.0	2 / 23	2018-12-20
2.0.0	2 / 26	2018-08-21
1.1.11	2 / 19	2018-03-01
1.1.10	2 / 19	2018-02-26
1.1.9	2 / 19	2018-02-21
1.1.8	2 / 19	2018-02-20
1.1.7	2 / 19	2018-02-19
1.1.6	2 / 19	2017-12-16
1.1.5	2 / 17	2017-10-05
1.1.4	2 / 17	2017-09-30
1.1.3	2 / 17	2017-09-30
1.1.2	2 / 17	2017-09-30
1.1.1	2 / 17	2017-09-30
1.1.0	2 / 16	2017-09-29
1.0.0	1 / 16	2017-07-26
0.11.2	1 / 3	2017-06-05
0.11.1	1 / 3	2017-04-01
0.11.0	1 / 3	2017-03-31
0.10.1	1 / 3	2017-02-25
0.10.0	1 / 3	2017-01-28
0.9.0	1 / 2	2016-06-20
0.8.5	1 / 2	2015-11-23
0.8.4	1 / 2	2015-05-24
0.8.3	1 / 2	2015-05-21
0.8.2	1 / 2	2015-05-21
0.8.1	1 / 2	2014-10-15
0.8.0	1 / 2	2014-10-11
0.7.2	2 / 2	2014-08-26
0.7.1	2 / 2	2014-08-25
0.7.0	1 / 3	2014-08-25
0.6.1	1 / 2	2014-08-04
0.5.1	1 / 0	2014-01-23
0.5.0	1 / 0	2013-02-01
0.1.2	0 / 0	2012-05-20
0.1.1	0 / 0	2012-05-13
0.1.0	0 / 0	2012-05-07

v6.2.0

1 finding

INFO No provenance attestation provenance

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

v4.3.0

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2019-11-21) provenance

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

INFO No provenance attestation provenance

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

v4.2.0

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2019-08-07) provenance

This version was published by a different npm account than previous versions on 2019-08-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v4.1.0

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2019-07-18) provenance

This version was published by a different npm account than previous versions on 2019-07-18. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v4.0.0

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2019-06-05) provenance

This version was published by a different npm account than previous versions on 2019-06-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.0.1

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2018-12-20) provenance

This version was published by a different npm account than previous versions on 2018-12-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v3.0.0

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2018-12-20) provenance

This version was published by a different npm account than previous versions on 2018-12-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v2.0.0

2 findings

HIGH Publisher changed: sokra → michael-ciniawsky (on 2018-08-21) provenance

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

INFO No provenance attestation provenance

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

v1.1.11

2 findings

HIGH Publisher changed: sokra → michael-ciniawsky (on 2018-03-01) provenance

This version was published by a different npm account than previous versions on 2018-03-01. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.1.10

2 findings

HIGH Publisher changed: sokra → michael-ciniawsky (on 2018-02-26) provenance

This version was published by a different npm account than previous versions on 2018-02-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.1.9

2 findings

HIGH Publisher changed: sokra → michael-ciniawsky (on 2018-02-21) provenance

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

INFO No provenance attestation provenance

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

v1.1.8

2 findings

HIGH Publisher changed: sokra → michael-ciniawsky (on 2018-02-20) provenance

This version was published by a different npm account than previous versions on 2018-02-20. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.1.7

2 findings

HIGH Publisher changed: sokra → michael-ciniawsky (on 2018-02-19) provenance

This version was published by a different npm account than previous versions on 2018-02-19. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.1.6

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-12-16) provenance

This version was published by a different npm account than previous versions on 2017-12-16. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.1.5

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-10-05) provenance

This version was published by a different npm account than previous versions on 2017-10-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v1.1.4

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-09-30) provenance

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

INFO No provenance attestation provenance

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

v1.1.3

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-09-30) provenance

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

INFO No provenance attestation provenance

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

v1.1.2

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-09-30) provenance

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

INFO No provenance attestation provenance

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

v1.1.1

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-09-30) provenance

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

INFO No provenance attestation provenance

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

v1.1.0

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-09-29) provenance

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

INFO No provenance attestation provenance

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

v1.0.0

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-07-26) provenance

This version was published by a different npm account than previous versions on 2017-07-26. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.11.2

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-06-05) provenance

This version was published by a different npm account than previous versions on 2017-06-05. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.11.1

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-04-01) provenance

This version was published by a different npm account than previous versions on 2017-04-01. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.11.0

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-03-31) provenance

This version was published by a different npm account than previous versions on 2017-03-31. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.10.1

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-02-25) provenance

This version was published by a different npm account than previous versions on 2017-02-25. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.10.0

2 findings

HIGH Publisher changed: sokra → d3viant0ne (on 2017-01-28) provenance

This version was published by a different npm account than previous versions on 2017-01-28. This could indicate a legitimate maintainer transition or an account compromise.

INFO No provenance attestation provenance

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

v0.9.0

1 finding

INFO No provenance attestation provenance

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

v0.8.5

1 finding

INFO No provenance attestation provenance

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

v0.8.4

1 finding

INFO No provenance attestation provenance

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

v0.8.3

1 finding

INFO No provenance attestation provenance

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

v0.8.2

1 finding

INFO No provenance attestation provenance

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

v0.8.1

1 finding

INFO No provenance attestation provenance

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

v0.8.0

1 finding

INFO No provenance attestation provenance

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

v0.7.2

1 finding

INFO No provenance attestation provenance

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

v0.7.1

1 finding

INFO No provenance attestation provenance

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

v0.7.0

1 finding

INFO No provenance attestation provenance

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

v0.6.1

1 finding

INFO No provenance attestation provenance

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

v0.5.1

1 finding

INFO No provenance attestation provenance

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

v0.5.0

1 finding

INFO No provenance attestation provenance

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

v0.1.2

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.