← Home

babel-preset-react

npm Repository Homepage

Babel preset for all React plugins.

17
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

amasadhzoojmmloganfsmythsebmckthejameskyle

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): hzoo and loganfsmyth are both known Babel core team maintainers; this 2017 transition is a legitimate handoff within the Babel project. ai
bogus-package bogus-package AI (bogus-package): Babel presets are intentionally tiny config packages; spam-publisher flags are false positives for Babel core team accounts publishing from the monorepo. ai
phantom-deps phantom-dep:babel-plugin-transform-react-jsx-self AI (phantom-deps): Babel presets reference plugins by name in config objects, not via require(); declared dependency is correct and expected for this package type. ai
phantom-deps phantom-dep:babel-plugin-transform-react-jsx-source AI (phantom-deps): Babel presets reference plugins by name in config objects, not via require(); declared dependency is correct and expected for this package type. ai

Versions (showing 17 of 17)

Version Deps Published
6.24.1 6 / 0
6.23.0 6 / 0
6.22.0 7 / 0
6.16.0 7 / 0
6.11.1 7 / 0
6.11.0 7 / 0
6.5.0 6 / 0
6.3.13 6 / 0
6.2.4 6 / 0
6.1.18 6 / 0
6.1.17 6 / 0
6.1.4 6 / 0
6.1.2 4 / 0
6.0.15 4 / 0
6.0.14 4 / 0
6.0.12 4 / 0
6.0.2 4 / 0

v6.24.1

2 findings
HIGH Publisher changed: loganfsmyth → hzoo (on 2017-04-07) provenance

This version was published by a different npm account than previous versions on 2017-04-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.23.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: hzoo → loganfsmyth (on 2017-02-14) provenance

[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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.16.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.5.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: sebmck → hzoo (on 2016-02-07) provenance

[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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.2.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v6.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.