url-loader MIT 31 versions

url-loader

npm Repository Homepage

A loader for webpack which transforms files into base64 URIs

31

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

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): sokra → d3viant0ne is a documented, legitimate webpack org maintainer transition in 2017; repo remains under webpack GitHub org. Stable false positive for this package.	ai	2026/04/22
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers (bebraw, d3viant0ne, ericclemmons, jhnns, thelarkinn) are known webpack core team members added during a legitimate org expansion in 2017.	ai	2026/04/22
bogus-package	bogus-package	AI (bogus-package): Inflated semver and mass-production signals are false positives: this is the legitimate webpack-contrib url-loader, a mature package with established versioning history published by known webpack team members.	ai	2026/04/21
dependencies	unvetted-dep:loader-utils	AI (dependencies): loader-utils is a standard webpack ecosystem dependency used by virtually all webpack loaders; expected and legitimate for this package.	ai	2026/04/21
dependencies	unvetted-dep:schema-utils	AI (dependencies): schema-utils is a standard webpack ecosystem dependency used by virtually all webpack loaders; expected and legitimate for this package.	ai	2026/04/21

Versions (showing 31 of 31)

Version	Deps	Published
4.1.1	3 / 24	2020-10-09
4.1.0	3 / 26	2020-04-08
4.0.0	3 / 25	2020-03-17
3.0.0	3 / 25	2019-11-26
2.3.0	3 / 25	2019-11-21
2.2.0	3 / 25	2019-10-04
2.1.0	3 / 25	2019-07-18
2.0.1	3 / 25	2019-06-25
2.0.0	3 / 25	2019-06-05
1.1.2	3 / 29	2018-10-10
1.1.1	3 / 29	2018-08-17
1.1.0	3 / 29	2018-08-14
1.0.1	3 / 27	2018-03-03
1.0.0	3 / 27	2018-03-03
0.6.2	3 / 1	2017-10-04
0.6.1	3 / 1	2017-10-04
0.6.0	3 / 1	2017-10-03
0.5.9	2 / 1	2017-06-12
0.5.8	2 / 0	2017-02-24
0.5.7	2 / 0	2015-11-23
0.5.6	2 / 0	2015-05-24
0.5.5	2 / 0	2014-04-02
0.5.4	2 / 0	2014-03-18
0.5.3	2 / 0	2014-01-23
0.5.2	2 / 0	2013-10-14
0.5.1	2 / 0	2013-02-13
0.5.0	1 / 0	2013-02-01
0.1.3	1 / 0	2012-07-19
0.1.2	0 / 0	2012-06-29
0.1.1	0 / 0	2012-05-20
0.1.0	0 / 0	2012-05-13

v4.1.1

1 finding

LOW No provenance attestation provenance

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

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

LOW No provenance attestation provenance

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

v2.2.0

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2019-10-04) provenance

This version was published by a different npm account than previous versions on 2019-10-04. 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

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.

LOW No provenance attestation provenance

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

v2.0.1

2 findings

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

This version was published by a different npm account than previous versions on 2019-06-25. 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

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.

LOW No provenance attestation provenance

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

v1.1.2

2 findings

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

This version was published by a different npm account than previous versions on 2018-10-10. 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.

v1.1.1

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2018-08-17) provenance

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

v1.1.0

2 findings

HIGH Publisher changed: sokra → evilebottnawi (on 2018-08-14) provenance

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

v1.0.1

2 findings

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

This version was published by a different npm account than previous versions on 2018-03-03. 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.

v1.0.0

2 findings

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

This version was published by a different npm account than previous versions on 2018-03-03. 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.

v0.6.2

2 findings

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

This version was published by a different npm account than previous versions on 2017-10-04. 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.

v0.6.1

2 findings

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

This version was published by a different npm account than previous versions on 2017-10-04. 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.

v0.6.0

2 findings

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

This version was published by a different npm account than previous versions on 2017-10-03. 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.

v0.5.9

2 findings

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

This version was published by a different npm account than previous versions on 2017-06-12. 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.

v0.5.8

2 findings

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

This version was published by a different npm account than previous versions on 2017-02-24. 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.

v0.5.7

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

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