@babel/helper-split-export-declaration
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; this is a routine maintainer rotation within the monorepo. | ai | |
| provenance | missing-githead | AI (provenance): Babel monorepo publish tooling change; gitHead absence is expected for this package and not a security signal. | ai | |
| provenance | no-provenance | AI (provenance): Babel packages from this era predate widespread Sigstore provenance adoption; stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo helpers share templated names, minimal descriptions, and no keywords by design. Stable false positive. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Babel helper packages commonly have empty descriptions; not indicative of malice for this scoped package. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 7.24.7 | 1 / 1 | |
| 7.24.6 | 1 / 1 | |
| 7.24.5 | 1 / 0 | |
| 7.22.6 | 1 / 0 | |
| 7.22.5 | 1 / 0 | |
| 7.18.6 | 1 / 0 | |
| 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.11 | 1 / 0 | |
| 7.11.0 | 1 / 0 | |
| 7.10.4 | 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.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.6
1 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.4
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.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.12.13
3 findingsThis 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.
[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.11
3 findingsThis version was published by a different npm account than previous versions on 2020-12-15. 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.
[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.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: jlhwung.
v7.10.4
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 2020-06-30. This could indicate a legitimate maintainer transition or an account compromise.
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 finding[Accepted risk] Package 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.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 2019-03-19. This could indicate a legitimate maintainer transition or an account compromise.
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.