← Home

babel-plugin-react-require

npm Repository Homepage

Babel plugin that adds React import declaration if file contains JSX tags.

15
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

timneutkensvslinko

Keywords

babelbabel-pluginreactjsx

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): vslinko is the original package author per package.json, GitHub repo, and email. The change from timneutkens back to vslinko reflects a legitimate ownership reversion, not a compromise. ai

Versions (showing 15 of 15)

Version Deps Published
4.0.3 0 / 11
4.0.2 0 / 8
4.0.1 0 / 8
4.0.0 0 / 8
3.1.3 0 / 20
3.1.2 0 / 19
3.1.1 0 / 23
3.1.0 0 / 21
3.0.2 0 / 20
3.0.1 0 / 20
3.0.0 0 / 20
2.1.0 0 / 18
2.0.0 0 / 15
1.0.2 0 / 1
1.0.1 0 / 1

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

v4.0.0

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.2

2 findings
HIGH Publisher changed: timneutkens → vslinko (on 2019-01-27) provenance

This version was published by a different npm account than previous versions on 2019-01-27. 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.

v3.0.1

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: vslinko → timneutkens (on 2018-10-01) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-10-01. This could indicate a legitimate maintainer transition or an account compromise.

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.