@babel/helper-hoist-variables
Helper function to hoist variables
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Babel monorepo publish pipeline change; nicolo-ribaudo is a trusted core Babel maintainer. Missing gitHead is a CI environment artifact, not a security signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Babel core package published by a highly trusted maintainer; lack of Sigstore attestation is not a risk signal here. | ai | |
| provenance | publisher-changed | AI (provenance): nicolo-ribaudo is a well-known Babel core team maintainer; the hzoo→nicolo-ribaudo transition is a documented legitimate handoff within the Babel project, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a core Babel maintainer with extensive history; addition is a legitimate team transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of xtuc is part of the documented Babel team restructuring; no evidence of compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo produces many templated helper packages by design; tiny payload and no keywords are expected for internal helper utilities. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 7.24.7 | 1 / 1 | |
| 7.24.6 | 1 / 1 | |
| 7.22.5 | 1 / 1 | |
| 7.18.6 | 1 / 1 | |
| 7.16.7 | 1 / 1 | |
| 7.16.0 | 1 / 1 | |
| 7.15.4 | 1 / 1 | |
| 7.14.5 | 1 / 1 | |
| 7.13.16 | 2 / 0 | |
| 7.13.0 | 2 / 0 | |
| 7.12.13 | 1 / 0 | |
| 7.10.4 | 1 / 0 | |
| 7.10.3 | 1 / 0 | |
| 7.10.1 | 1 / 0 | |
| 7.8.3 | 1 / 0 | |
| 7.8.0 | 1 / 0 | |
| 7.7.4 | 1 / 0 | |
| 7.7.0 | 1 / 0 | |
| 7.4.4 | 1 / 0 | |
| 7.4.0 | 1 / 0 | |
| 7.0.0 | 1 / 0 |
v7.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.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: nicolo-ribaudo.
v7.15.4
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: nicolo-ribaudo.
v7.14.5
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: nicolo-ribaudo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.16
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: nicolo-ribaudo.
v7.13.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: nicolo-ribaudo.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.13
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: nicolo-ribaudo.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-02-03. This could indicate a legitimate maintainer transition or an account compromise.
v7.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.3
2 findingsThis version was published by a different npm account than previous versions on 2020-06-19. 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.
v7.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
2 findingsThis version was published by a different npm account than previous versions on 2019-03-19. 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.
v7.0.0
2 findingsPackage 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 2018-08-27. This could indicate a legitimate maintainer transition or an account compromise.