@babel/plugin-transform-function-name
Apply ES2015 function.name semantics to all functions
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 | publisher-changed | AI (provenance): nicolo-ribaudo is a well-known Babel core team member; the hzoo→nicolo-ribaudo transition is a documented legitimate maintainer handoff within the Babel project. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): nicolo-ribaudo is a core Babel contributor; addition is a legitimate team transition, not a suspicious takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects Babel monorepo structure; tiny payload is expected for a focused Babel transform plugin. Not indicative of spam or malice. | ai | |
| provenance | no-provenance | AI (provenance): Babel packages at this version era predate standard Sigstore provenance; absence is expected and not a risk signal for this publisher. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead reflects a CI/publish environment change in the Babel monorepo, not a supply chain risk. Trusted publisher with long track record. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 7.29.7 | 3 / 2 | |
| 7.27.1 | 3 / 2 | |
| 7.25.9 | 3 / 2 | |
| 7.25.7 | 3 / 2 | |
| 7.25.1 | 3 / 2 | |
| 7.25.0 | 3 / 2 | |
| 7.24.7 | 3 / 2 | |
| 7.24.6 | 3 / 2 | |
| 7.24.1 | 3 / 2 | |
| 7.23.3 | 3 / 2 | |
| 7.22.5 | 3 / 2 | |
| 7.18.9 | 3 / 2 | |
| 7.18.6 | 3 / 2 | |
| 7.16.7 | 3 / 2 | |
| 7.16.5 | 2 / 2 | |
| 7.16.0 | 2 / 2 | |
| 7.14.5 | 2 / 2 | |
| 7.12.13 | 2 / 2 | |
| 7.12.1 | 2 / 2 | |
| 7.10.4 | 2 / 2 | |
| 7.10.1 | 2 / 2 | |
| 7.8.3 | 2 / 2 | |
| 7.8.0 | 2 / 2 | |
| 7.7.4 | 2 / 2 | |
| 7.7.0 | 2 / 2 | |
| 7.4.4 | 2 / 2 | |
| 7.4.3 | 2 / 2 | |
| 7.2.0 | 2 / 2 | |
| 7.1.0 | 2 / 2 | |
| 7.0.0 | 2 / 2 |
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.25.1
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.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.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.7
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.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 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 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.
[Accepted risk] 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.
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 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
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.3
1 findingPackage 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.
[Accepted risk] 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.