@babel/plugin-transform-arrow-functions
Compile ES2015 arrow functions to ES5
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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 publish pipeline does not consistently include gitHead; this is a known artifact for @babel/* packages, not a tampering signal. | ai | |
| provenance | no-provenance | AI (provenance): This version was published in 2021, before Sigstore provenance was available for npm packages. Not a risk for this package. | ai | |
| provenance | publisher-changed | AI (provenance): nicolo-ribaudo is a known Babel core maintainer; this is a legitimate team transition, not a suspicious account change. Stable for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo produces many similarly-named small plugin packages by design; mass-production and tiny-payload signals are expected and benign for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 1 / 4 | |
| 7.27.1 | 1 / 4 | |
| 7.25.9 | 1 / 4 | |
| 7.25.7 | 1 / 4 | |
| 7.24.7 | 1 / 4 | |
| 7.24.6 | 1 / 4 | |
| 7.24.1 | 1 / 4 | |
| 7.23.3 | 1 / 4 | |
| 7.22.5 | 1 / 4 | |
| 7.21.5 | 1 / 4 | |
| 7.20.7 | 1 / 4 | |
| 7.18.6 | 1 / 4 | |
| 7.17.12 | 1 / 4 | |
| 7.16.7 | 1 / 4 | |
| 7.16.5 | 1 / 4 | |
| 7.16.0 | 1 / 3 | |
| 7.14.5 | 1 / 3 | |
| 7.13.0 | 1 / 3 | |
| 7.12.13 | 1 / 3 | |
| 7.12.1 | 1 / 3 | |
| 7.10.4 | 1 / 3 | |
| 7.10.1 | 1 / 3 | |
| 7.8.3 | 1 / 3 | |
| 7.8.0 | 1 / 3 | |
| 7.7.4 | 1 / 3 | |
| 7.2.0 | 1 / 3 | |
| 7.0.0 | 1 / 3 | |
| 8.0.0-rc.3 | 1 / 4 | |
| 8.0.0-rc.2 | 1 / 4 | |
| 8.0.0-rc.1 | 1 / 4 | |
| 8.0.0-beta.4 | 1 / 4 | |
| 7.0.0-beta.46 | 1 / 3 |
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.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.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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.3
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.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.7
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.17.12
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 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.16.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: nicolo-ribaudo.
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.13.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: nicolo-ribaudo.
v7.12.13
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.1
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-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.
v7.10.4
2 findingsPackage 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 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.2.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-12-03. This could indicate a legitimate maintainer transition or an account compromise.
v7.0.0
2 findingsPackage 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.