@babel/helper-builder-react-jsx-experimental
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): jlhwung is a long-standing Babel core team member (3368 days, 5413 approved packages). Publisher rotation within the Babel org is expected and not a compromise signal. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jlhwung is a verified Babel core contributor; addition is a legitimate team maintainer transition within the official babel/babel monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): hzoo, loganfsmyth, and danez are legitimate Babel core team members; mass-produced similarly-named packages are expected for the Babel monorepo. No spam indicators apply here. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is a minor publish environment artifact for Babel monorepo packages; not a security signal for this well-established package. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation was not standard at time of publish; expected for older Babel releases. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.12.11 | 3 / 0 | |
| 7.12.10 | 3 / 0 | |
| 7.12.4 | 3 / 0 | |
| 7.12.1 | 3 / 0 | |
| 7.12.0 | 3 / 0 | |
| 7.11.5 | 3 / 0 | |
| 7.10.5 | 3 / 0 | |
| 7.10.4 | 3 / 0 | |
| 7.10.1 | 3 / 0 | |
| 7.9.5 | 3 / 0 | |
| 7.9.0 | 3 / 0 |
v7.12.11
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.
Matched 3 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: hzoo, loganfsmyth, danez. • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'loganfsmyth' owns 167 packages, ≥70% share a templated name shape. • [S_NO_KEYWORDS] No keywords declared.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.10
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.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.12.1
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.0
3 findingsThis version was published by a different npm account than previous versions on 2020-10-14. 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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.5
1 finding[Accepted risk] 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.