@babel/helper-wrap-function
Helper to wrap functions inside a function call.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Babel monorepo packages from this era commonly lack gitHead; trusted publisher nicolo-ribaudo with strong track record. Not indicative of supply chain compromise. | ai | |
| provenance | no-provenance | AI (provenance): This version predates Sigstore provenance adoption; absence of attestation is expected for this era of Babel releases. | ai | |
| provenance | publisher-changed | AI (provenance): nicolo-ribaudo is a well-known Babel core maintainer; the transition from hzoo is a legitimate team handoff within the Babel project, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a recognized Babel core contributor; this addition is a legitimate maintainer transition within the Babel monorepo team. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): @babel/traverse is a declared dependency used by convention in Babel helper packages; phantom-dep finding is a stable false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo produces many similarly-named scoped packages by design; mass-production and no-keywords signals are expected false positives for this ecosystem. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 3 / 0 | |
| 7.28.6 | 3 / 0 | |
| 7.28.3 | 3 / 0 | |
| 7.27.1 | 3 / 0 | |
| 7.25.9 | 3 / 0 | |
| 7.25.7 | 3 / 0 | |
| 7.25.0 | 3 / 0 | |
| 7.24.7 | 4 / 0 | |
| 7.24.6 | 3 / 1 | |
| 7.24.5 | 3 / 1 | |
| 7.22.20 | 3 / 1 | |
| 7.22.17 | 3 / 1 | |
| 7.22.10 | 3 / 1 | |
| 7.22.9 | 3 / 1 | |
| 7.22.5 | 4 / 0 | |
| 7.20.5 | 4 / 0 | |
| 7.19.0 | 4 / 0 | |
| 7.18.11 | 4 / 0 | |
| 7.18.10 | 4 / 0 | |
| 7.18.9 | 4 / 0 | |
| 7.18.6 | 4 / 0 | |
| 7.16.8 | 4 / 0 | |
| 7.16.7 | 4 / 0 | |
| 7.16.5 | 4 / 0 | |
| 7.16.0 | 4 / 0 | |
| 7.15.4 | 4 / 0 | |
| 7.14.5 | 4 / 0 | |
| 7.13.0 | 4 / 0 | |
| 7.12.13 | 4 / 0 | |
| 7.12.3 | 4 / 0 | |
| 7.10.4 | 4 / 0 | |
| 7.10.1 | 4 / 0 | |
| 7.8.3 | 4 / 0 | |
| 7.8.0 | 4 / 0 | |
| 7.7.4 | 4 / 0 | |
| 7.7.0 | 4 / 0 | |
| 7.2.0 | 4 / 0 | |
| 7.1.0 | 4 / 0 | |
| 7.0.0 | 4 / 0 |
v7.29.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.9
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.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.10
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.8
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. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.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.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 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.13.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.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.3
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.10.4
2 findingsThis 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.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.4
2 findingsThis version was published by a different npm account than previous versions on 2019-11-22. 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.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.2.0
2 findingsThis version was published by a different npm account than previous versions on 2018-12-03. 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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.