@babel/helper-get-function-arity
Helper function to get function arity
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): Both jlhwung and nicolo-ribaudo are known Babel core team members; publisher rotation within the org is expected. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo produces many small helper packages by design; mass-production, tiny payload, and no-keywords signals are expected. | ai | |
| provenance | missing-githead | AI (provenance): Babel monorepo publish tooling change; trusted publisher nicolo-ribaudo; no security concern from missing gitHead. | ai | |
| provenance | no-provenance | AI (provenance): Published before Sigstore provenance was standard practice; trusted Babel maintainer. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.16.7 | 1 / 0 | |
| 7.16.0 | 1 / 0 | |
| 7.15.4 | 1 / 0 | |
| 7.14.5 | 1 / 0 | |
| 7.12.13 | 1 / 0 | |
| 7.12.10 | 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.0.0 | 1 / 0 |
v7.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.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.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 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.12.13
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.10
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.
This version was published by a different npm account than previous versions on 2020-12-09. 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.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.
[Accepted risk] 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.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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
2 findingsThis version was published by a different npm account than previous versions on 2019-11-05. 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 findings[Accepted risk] Package 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.