babel-helper-builder-react-jsx
Helper function to build react jsx
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): Transition from loganfsmyth to hzoo — both are well-known Babel core maintainers. Legitimate handoff. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Babel monorepo produces many packages with templated names; no-keywords is normal for internal helpers. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is declared in dependencies; phantom-dep is a false positive for this Babel helper's usage pattern. | ai | |
| phantom-deps | phantom-dep:babel-runtime | AI (phantom-deps): babel-runtime is declared in dependencies; used via Babel transform, not direct import. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 6.26.0 | 3 / 0 | |
| 6.24.1 | 3 / 0 | |
| 6.23.0 | 4 / 0 | |
| 6.22.0 | 4 / 0 | |
| 6.21.1 | 4 / 0 | |
| 6.21.0 | 4 / 0 | |
| 6.18.0 | 4 / 0 | |
| 6.9.0 | 4 / 0 | |
| 6.8.0 | 4 / 0 | |
| 6.7.5 | 4 / 0 | |
| 6.6.5 | 4 / 0 | |
| 6.6.4 | 4 / 0 | |
| 6.5.0 | 4 / 0 | |
| 6.3.13 | 4 / 0 | |
| 6.2.4 | 4 / 0 | |
| 6.2.0 | 4 / 0 | |
| 6.1.18 | 4 / 0 | |
| 6.1.17 | 4 / 0 | |
| 6.1.16 | 4 / 0 | |
| 6.1.13 | 4 / 0 | |
| 6.1.12 | 4 / 0 | |
| 6.1.11 | 4 / 0 | |
| 6.1.10 | 4 / 0 | |
| 6.1.9 | 4 / 0 | |
| 6.1.8 | 4 / 0 | |
| 6.1.7 | 4 / 0 | |
| 6.1.6 | 4 / 0 | |
| 6.1.5 | 4 / 0 | |
| 6.0.15 | 4 / 0 | |
| 6.0.14 | 4 / 0 | |
| 6.0.2 | 4 / 0 | |
| 6.0.0 | 4 / 0 |
v6.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.23.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 2017-02-14. This could indicate a legitimate maintainer transition or an account compromise.
v6.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.21.1
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 2016-12-18. This could indicate a legitimate maintainer transition or an account compromise.
v6.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
2 findingsThis version was published by a different npm account than previous versions on 2016-05-02. 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.
v6.7.5
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 2016-04-08. This could indicate a legitimate maintainer transition or an account compromise.
v6.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.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 2016-02-07. This could indicate a legitimate maintainer transition or an account compromise.
v6.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.