babel-preset-minify
Babel preset for all minify plugins.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require of 'babel-plugin-' + name is the canonical Babel preset pattern for loading declared plugin dependencies. Not arbitrary code loading. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is an intentional initial release by a well-established publisher (jongleberry) with a clear GitHub repo and legitimate purpose. Not a throwaway malicious package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-merge-sibling-variables | AI (phantom-deps): Loaded dynamically via the Babel preset pattern; declared as a direct dependency in package.json. Not a true phantom dependency. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-property-literals | AI (phantom-deps): Loaded dynamically via the Babel preset pattern; declared as a direct dependency in package.json. Not a true phantom dependency. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-member-expression-literals | AI (phantom-deps): Loaded dynamically via the Babel preset pattern; declared as a direct dependency in package.json. Not a true phantom dependency. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence is expected for this era of publishing and does not indicate risk. | ai | |
| provenance | missing-githead | AI (provenance): Established Babel ecosystem package with trusted publisher; missing gitHead is a process artifact, not a security signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): nicolo-ribaudo is a known Babel core team member; this is a legitimate maintainer transition within the Babel org, not a compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo (Henry Zhu) and loganfsmyth (Logan Smyth) are well-known legitimate Babel core contributors; spam flag is a false positive for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): babeljs team account removal is consistent with Babel org consolidating maintenance under individual contributors. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a well-established Babel core contributor; addition is a legitimate org-level transition. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.5.2 | 23 / 0 | |
| 0.5.1 | 23 / 0 | |
| 0.5.0 | 23 / 0 | |
| 0.4.3 | 23 / 0 | |
| 0.4.2 | 23 / 0 | |
| 0.4.1 | 23 / 0 | |
| 0.4.0 | 23 / 0 | |
| 0.3.0 | 23 / 0 | |
| 0.2.0 | 23 / 0 | |
| 0.0.0 | 3 / 6 |
v0.5.2
2 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boopathi.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boopathi.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boopathi.
v0.2.0
3 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: boopathi.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-08-14. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.