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 | publisher-changed | AI (provenance): Legitimate transition from sebmck (Sebastian McKenzie) to hzoo (Henry Zhu), both core Babel maintainers. Well-documented handoff across the entire Babel monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: tiny payload and no keywords are normal for a Babel monorepo helper; mass-production signal reflects the monorepo structure, not spam. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2016, before Sigstore provenance existed. Expected for legacy Babel 6.x packages. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 6.24.1 | 2 / 0 | |
| 6.22.0 | 2 / 0 | |
| 6.18.0 | 2 / 0 | |
| 6.8.0 | 2 / 0 | |
| 6.6.5 | 2 / 0 | |
| 6.6.4 | 2 / 0 | |
| 6.5.0 | 2 / 0 | |
| 6.3.13 | 2 / 0 | |
| 6.2.4 | 2 / 0 | |
| 6.1.18 | 2 / 0 | |
| 6.1.17 | 2 / 0 | |
| 6.1.16 | 2 / 0 | |
| 6.1.13 | 2 / 0 | |
| 6.1.12 | 2 / 0 | |
| 6.1.10 | 2 / 0 | |
| 6.1.9 | 2 / 0 | |
| 6.1.8 | 2 / 0 | |
| 6.1.7 | 2 / 0 | |
| 6.1.6 | 2 / 0 | |
| 6.1.5 | 2 / 0 | |
| 6.0.15 | 2 / 0 | |
| 6.0.14 | 2 / 0 | |
| 6.0.2 | 2 / 0 | |
| 6.0.0 | 2 / 0 |
v6.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.4
2 findingsThis version was published by a different npm account than previous versions on 2016-03-02. 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.
v6.5.0
2 findingsThis version was published by a different npm account than previous versions on 2016-02-07. 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.
v6.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.