@babel/helper-call-delegate
Helper function to call delegate
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): hzoo → nicolo-ribaudo is a well-documented Babel team maintainer transition; stable for all @babel packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a known Babel core team member; legitimate maintainer addition. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): @babel/traverse is declared in deps and used internally by Babel helpers; framework-scoped convention. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel core team members (hzoo, loganfsmyth, danez) are not spam; monorepo naming convention triggers mass-production heuristic. Stable FP for @babel/* packages. | ai | |
| provenance | missing-githead | AI (provenance): Babel monorepo publish workflow change dropped gitHead; not a security signal for this established package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 7.12.13 | 2 / 1 | |
| 7.12.1 | 2 / 1 | |
| 7.11.4 | 2 / 1 | |
| 7.10.4 | 3 / 0 | |
| 7.10.3 | 3 / 0 | |
| 7.10.1 | 3 / 0 | |
| 7.8.7 | 3 / 0 | |
| 7.8.3 | 3 / 0 | |
| 7.8.0 | 3 / 0 | |
| 7.7.4 | 3 / 0 | |
| 7.7.0 | 3 / 0 | |
| 7.4.4 | 3 / 0 | |
| 7.4.0 | 3 / 0 | |
| 7.1.0 | 3 / 0 | |
| 7.0.0 | 3 / 0 |
v7.12.13
3 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.
Matched 3 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: hzoo, loganfsmyth, danez. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_NO_KEYWORDS] No keywords declared.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
3 findingsThis version was published by a different npm account than previous versions on 2020-10-15. 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.
[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.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage 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 findingPackage 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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.