@babel/helper-environment-visitor
Helper visitor to only visit nodes in the current 'this' context
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): All signals are false positives for a Babel monorepo helper: mass-production naming is expected, tiny payload is normal for focused helpers, inflated semver matches Babel's versioning strategy, and no keywords is common in monorepo sub-packages. | ai | |
| provenance | no-provenance | AI (provenance): This version predates widespread Sigstore provenance adoption on npm; absence is expected for packages published in this era. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.24.7 | 1 / 1 | |
| 7.24.6 | 0 / 2 | |
| 7.22.20 | 0 / 2 | |
| 7.22.5 | 0 / 2 | |
| 7.22.1 | 0 / 2 | |
| 7.21.5 | 0 / 2 | |
| 7.18.9 | 0 / 2 | |
| 7.18.6 | 0 / 2 | |
| 7.18.2 | 0 / 2 | |
| 7.16.7 | 1 / 1 | |
| 7.16.5 | 1 / 1 |
v7.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.9
1 findingPackage 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.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.