uglifyjs-webpack-plugin MIT 45 versions

uglifyjs-webpack-plugin

npm Repository Homepage

UglifyJS plugin for webpack

45

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

bebrawd3viant0neevilebottnawijhnnsmichael-ciniawskysokrathelarkinn

Keywords

uglifyuglify-jsuglify-eswebpackwebpack-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate maintainer transition within webpack-contrib team; michael-ciniawsky is a known webpack-contrib member with strong track record.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): michael-ciniawsky is a known webpack-contrib maintainer; legitimate team addition.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): Small dist/cjs.js is a re-export entry point (common pattern); thelarkinn mass-production reflects webpack ecosystem naming, not spam.	ai	2026/04/24

Versions (showing 45 of 45)

Version	Deps	Published
2.2.0	9 / 25	2019-07-31
2.1.3	9 / 24	2019-05-15
2.1.2	8 / 24	2019-02-25
2.1.1	8 / 26	2018-12-27
2.1.0	8 / 26	2018-12-22
2.0.1	8 / 26	2018-09-18
2.0.0	8 / 26	2018-09-14
1.3.0	8 / 20	2018-08-14
1.2.7	8 / 18	2018-06-25
1.2.6	8 / 18	2018-06-20
1.2.5	8 / 18	2018-04-18
1.2.4	8 / 18	2018-03-16
1.2.3	8 / 18	2018-03-10
1.2.2	8 / 18	2018-02-24
1.2.1	8 / 18	2018-02-23
1.2.0	8 / 18	2018-02-16
1.1.8	8 / 18	2018-01-29
1.1.7	8 / 18	2018-01-29
1.1.6	8 / 18	2018-01-05
1.1.5	8 / 18	2017-12-27
1.1.4	8 / 18	2017-12-14
1.1.3	8 / 18	2017-12-14
1.1.2	7 / 18	2017-11-30
1.1.1	7 / 18	2017-11-23
1.1.0	7 / 18	2017-11-19
1.0.1	7 / 18	2017-10-24
1.0.0	7 / 18	2017-10-23
0.4.6	3 / 17	2017-06-19
0.4.5	2 / 18	2017-06-19
0.4.4	2 / 18	2017-06-18
0.4.3	2 / 18	2017-04-15
0.4.2	2 / 18	2017-04-12
0.4.1	2 / 18	2017-04-05
0.4.0	2 / 18	2017-03-30
0.3.1	2 / 17	2017-03-22
0.3.0	2 / 17	2017-03-04
0.2.2	2 / 17	2017-03-02
0.2.1	2 / 17	2017-02-20
0.2.0	2 / 17	2017-02-19
0.1.5	2 / 16	2017-02-15
0.1.4	2 / 16	2017-02-06
0.1.3	2 / 16	2017-02-02
0.1.2	2 / 16	2017-01-25
0.1.1	2 / 16	2017-01-25
0.1.0	2 / 16	2017-01-24

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.3

1 finding

LOW No provenance attestation provenance

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

v2.1.2

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.7

1 finding

LOW No provenance attestation provenance

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

v1.2.6

2 findings

HIGH Publisher changed: michael-ciniawsky → evilebottnawi (on 2018-06-20) provenance

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

2 findings

HIGH Publisher changed: michael-ciniawsky → d3viant0ne (on 2018-04-18) provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

1 finding

LOW No provenance attestation provenance

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

v1.1.8

2 findings

HIGH Publisher changed: d3viant0ne → michael-ciniawsky (on 2018-01-29) provenance

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

2 findings

HIGH Publisher changed: d3viant0ne → michael-ciniawsky (on 2018-01-29) provenance

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

2 findings

HIGH Publisher changed: d3viant0ne → michael-ciniawsky (on 2018-01-05) provenance

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

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings

HIGH Publisher changed: thelarkinn → d3viant0ne (on 2017-10-23) provenance

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