babel-plugin-minify-infinity

## Example

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

babeljsboopathihzoologanfsmythvignesh.shanmugam

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): Legitimate transition from amasad to kangax within the official Babel minify project; both are known Babel team members.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): boopathi, hzoo, kangax are all recognized Babel core team members; legitimate team expansion.	ai	2026/04/24

Versions (showing 11 of 11)

Version	Deps	Published
0.4.3	0 / 0	2018-05-14
0.4.2	0 / 0	2018-05-14
0.4.1	0 / 0	2018-05-03
0.4.0	0 / 0	2018-04-08
0.3.0	0 / 0	2018-01-31
0.2.0	0 / 0	2017-08-14
0.1.2	0 / 0	2017-06-13
0.1.1	0 / 0	2017-05-22
0.1.0	0 / 0	2017-05-22
0.0.3	0 / 0	2016-11-18
0.0.1	0 / 0	2016-08-26

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

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-05-22) provenance

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

v0.0.3

2 findings

HIGH Publisher changed: amasad → kangax (on 2016-11-18) provenance

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

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.