← Home

babel-plugin-react-transform

npm Repository Homepage

Babel plugin to instrument React components with custom transforms

12
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

thejameskylegaearon

Keywords

babel-pluginreact-transforminstrumentationdxreactreactjscomponents

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): gaearon→thejameskyle is a well-known legitimate maintainer transition between prominent React/Babel ecosystem contributors. ai
maintainer-change maintainer-added AI (maintainer-change): thejameskyle (James Kyle) is a known Babel core team member; legitimate addition as maintainer. ai
source-diff large-new-source-files AI (source-diff): Major version bump (Babel 5→6 migration) naturally adds restructured source and test fixtures. ai

Versions (showing 12 of 12)

Version Deps Published
3.0.0 1 / 9
2.0.2 1 / 9
2.0.1 1 / 9
2.0.0 1 / 9
1.1.1 1 / 3
1.1.0 1 / 3
1.0.5 1 / 3
1.0.4 1 / 2
1.0.3 1 / 2
1.0.2 0 / 2
1.0.1 0 / 2
1.0.0 0 / 2

v3.0.0

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

2 findings
HIGH Publisher changed: gaearon → thejameskyle (on 2015-12-23) provenance

This version was published by a different npm account than previous versions on 2015-12-23. 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.