babel-plugin-minify-dead-code-elimination MIT 22 versions

babel-plugin-minify-dead-code-elimination

npm Repository Homepage

Inlines bindings when possible. Tries to evaluate expressions and prunes unreachable as a result.

22

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

nicolo-ribaudoboopathihzoovignesh.shanmugamloganfsmyth

Keywords

babel-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): nicolo-ribaudo is a known Babel core team maintainer; the hzoo → nicolo-ribaudo transition is a legitimate handoff within the Babel organization.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): nicolo-ribaudo is a well-established Babel core maintainer; addition is a legitimate team transition, not a takeover.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): babeljs org account removal is consistent with Babel team restructuring; no malicious signal.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): hzoo and loganfsmyth are legitimate Babel project maintainers, not spam publishers. False positive for this package.	ai	2026/04/23

Versions (showing 22 of 22)

Version	Deps	Published
0.5.2	4 / 0	2022-05-06
0.5.1	4 / 0	2019-08-15
0.5.0	4 / 0	2018-09-24
0.4.3	4 / 0	2018-05-14
0.4.2	4 / 0	2018-05-14
0.4.1	4 / 0	2018-05-03
0.4.0	4 / 0	2018-04-08
0.3.0	4 / 0	2018-01-31
0.2.0	4 / 0	2017-08-14
0.1.7	3 / 0	2017-06-13
0.1.6	3 / 0	2017-05-22
0.1.5	3 / 0	2017-05-22
0.1.4	3 / 0	2017-03-03
0.1.3	3 / 0	2017-02-08
0.1.2	2 / 0	2017-01-17
0.1.1	2 / 0	2016-11-21
0.1.0	2 / 0	2016-10-31
0.0.5	2 / 0	2016-11-21
0.0.4	2 / 0	2016-10-07
0.0.3	2 / 0	2016-09-30
0.0.2	2 / 0	2016-09-20
0.0.1	2 / 0	2016-08-26

v0.5.2

2 findings

HIGH Publisher changed: hzoo → nicolo-ribaudo (on 2022-05-06) provenance

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

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: boopathi → hzoo (on 2019-08-15) provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

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

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: kangax → boopathi (on 2017-02-08) provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.5

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: hzoo → kangax (on 2016-11-21) provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

LOW No provenance attestation provenance

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

v0.0.2

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: amasad → hzoo (on 2016-09-20) provenance

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

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