babel-plugin-external-helpers
This plugin contains helper functions that’ll be placed at the top of the generated code
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): babel-runtime is the standard Babel 6.x runtime helper dependency, expected for all Babel 6.x plugins. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): This was the well-documented absorption of the package into the official Babel monorepo in 2016. New maintainers are the Babel core team. Not a hijack. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from monastic.panic to hzoo reflects the legitimate transfer to the Babel core team in 2016. hzoo is a known Babel maintainer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are all Babel core team members (amasad, hzoo, jmm, loganfsmyth, sebmck, thejameskyle). Legitimate project transfer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of monastic.panic is part of the documented transfer to the Babel core team. Not indicative of a hostile takeover. | ai | |
| provenance | missing-githead | AI (provenance): Established Babel monorepo package; missing gitHead reflects older publish tooling, not a security concern. Consistent across the package's history. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is a standard Babel 6 dependency pattern; runtime helpers are injected at transform time, not directly imported. This is expected behavior for Babel 6 plugins. | ai | |
| provenance | no-provenance | AI (provenance): Babel 6 era package (~2017); Sigstore provenance did not exist at publish time. Not a meaningful risk signal for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel core team members (hzoo, sebmck, thejameskyle, loganfsmyth) are flagged as spam publishers, but these are well-known legitimate Babel project maintainers. Tiny payload is expected for a single-purpose Babel plugin. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.22.0 | 1 / 1 | |
| 6.18.0 | 1 / 1 | |
| 6.8.0 | 1 / 1 | |
| 6.5.0 | 1 / 1 | |
| 6.4.0 | 1 / 1 | |
| 1.1.1 | 0 / 0 | |
| 1.1.0 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v6.22.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: hzoo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.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: hzoo.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.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: hzoo.
v6.5.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: hzoo.
v6.4.0
4 findingsAll previous maintainers (monastic.panic) were replaced by new maintainers (amasad, hzoo, jmm, loganfsmyth, sebmck, thejameskyle). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2016-01-06. This could indicate a legitimate maintainer transition or an account compromise.
[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: hzoo.