react-addons-test-utils
This package provides the React TestUtils add-on.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 findingsThis 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[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.