gulp-babel-minify MIT 26 versions

gulp-babel-minify

npm Repository Homepage

Babel Minify plugin for Gulp

26

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-minifybabel-preset

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Transition from boopathi to hzoo is a known legitimate Babel team maintainer handoff; hzoo (Henry Zhu) is a core Babel maintainer with a strong track record.	ai	2026/04/24
npm-metadata	suspicious-initial-version	AI (npm-metadata): Version 0.0.0 is a namespace reservation by trusted publisher boopathi (565 approved packages, 0 rejected). No malicious content present.	ai	2026/04/24
npm-metadata	no-description	AI (npm-metadata): Placeholder package by trusted publisher; missing description is consistent with namespace reservation, not malicious intent.	ai	2026/04/24
bogus-package	bogus-package	AI (bogus-package): hzoo (Henry Zhu) and loganfsmyth are well-known Babel core contributors, not spam publishers. This is a false positive for this package.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): nicolo-ribaudo is a Babel core team member; adding them as maintainer of a Babel monorepo package is a legitimate transition.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of babeljs org account is consistent with Babel team restructuring maintainership to individual contributors.	ai	2026/04/23

Versions (showing 26 of 26)

Version	Deps	Published
0.5.2	5 / 0	2022-05-06
0.5.1	5 / 0	2019-08-15
0.5.0	5 / 0	2018-09-24
0.4.3	5 / 0	2018-05-14
0.4.2	5 / 0	2018-05-14
0.4.1	5 / 0	2018-05-03
0.4.0	5 / 0	2018-04-08
0.3.0	5 / 0	2018-01-31
0.2.0	5 / 0	2017-08-14
0.1.12	2 / 0	2016-07-06
0.1.11	2 / 0	2016-07-03
0.1.10	2 / 0	2016-07-03
0.1.9	2 / 0	2016-07-03
0.1.8	2 / 0	2016-06-30
0.1.7	2 / 0	2016-06-30
0.1.6	2 / 0	2016-06-29
0.1.5	2 / 0	2016-06-29
0.1.4	2 / 0	2016-06-14
0.1.3	2 / 0	2016-06-09
0.1.2	2 / 0	2016-06-09
0.1.1	2 / 0	2016-06-09
0.1.0	2 / 0	2016-06-07
0.0.7	2 / 0	2016-06-02
0.0.6	2 / 0	2016-06-02
0.0.1	2 / 0	2016-06-02
0.0.0	0 / 0	2016-06-02

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

HIGH Publisher changed: boopathi → hzoo (on 2019-08-15) provenance

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.

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

1 finding

LOW No provenance attestation provenance

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

v0.1.11

1 finding

LOW No provenance attestation provenance

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

v0.1.10

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

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

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

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

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

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