← Home

react-addons-test-utils

This package provides the React TestUtils add-on.

25
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

sophiebitstrueadmgaearonbrianvaughnfb

Keywords

reactreact-addon

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
bogus-package bogus-package AI (bogus-package): react-addons-test-utils is an official Facebook/React shim. Tiny payload and minimal README are by design; fb/gaearon spam flags are false positives for official React npm accounts. ai
provenance publisher-changed AI (provenance): sophiebits (Sophie Alpert) is a known React core team member; this is a documented legitimate maintainer transition within the Facebook/React team. ai
maintainer-change maintainer-added AI (maintainer-change): sophiebits is a known React core team member; addition is a legitimate internal team transition. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers are all known React core contributors; reflects a documented consolidation of the React npm publishing team. ai

Versions (showing 25 of 25)

Version Deps Published
15.6.2 0 / 3
15.6.0 0 / 3
15.5.1 2 / 3
15.5.0 2 / 3
15.4.2 2 / 0
15.4.1 0 / 0
15.4.0 0 / 0
15.3.2 0 / 0
15.3.1 0 / 0
15.3.0 0 / 0
15.2.1 0 / 0
15.2.0 0 / 0
15.1.0 0 / 0
15.0.2 0 / 0
15.0.1 0 / 0
15.0.0 0 / 0
0.14.8 0 / 0
0.14.7 0 / 0
0.14.6 0 / 0
0.14.5 0 / 0
0.14.4 0 / 0
0.14.3 0 / 0
0.14.2 0 / 0
0.14.1 0 / 0
0.14.0 0 / 0

v15.6.2

2 findings
HIGH Publisher changed: gaearon → sophiebits (on 2017-09-26) provenance

This version was published by a different npm account than previous versions on 2017-09-26. 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.

v15.6.0

1 finding
LOW No provenance attestation provenance

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

v15.5.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: brianvaughn → gaearon (on 2017-04-09) provenance

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

v15.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: gaearon → brianvaughn (on 2017-04-07) provenance

[Accepted risk] 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.

v15.4.2

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: spicyj → gaearon (on 2017-01-06) provenance

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

v15.4.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: tomocchino → spicyj (on 2016-11-23) provenance

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

v15.4.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: zpao → tomocchino (on 2016-11-16) provenance

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

v15.3.2

1 finding
LOW No provenance attestation provenance

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

v15.3.1

1 finding
LOW No provenance attestation provenance

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

v15.3.0

1 finding
LOW No provenance attestation provenance

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

v15.2.1

1 finding
LOW No provenance attestation provenance

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

v15.2.0

1 finding
LOW No provenance attestation provenance

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

v15.1.0

1 finding
LOW No provenance attestation provenance

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

v15.0.2

1 finding
LOW No provenance attestation provenance

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

v15.0.1

1 finding
LOW No provenance attestation provenance

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

v15.0.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: gaearon → zpao (on 2016-04-07) provenance

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