react
React is a JavaScript library for building user interfaces.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): React's publish pipeline legitimately may not include gitHead; this is not a security concern for the canonical react package. | ai | |
| provenance | no-provenance | AI (provenance): React has historically published without Sigstore provenance; not a security risk for this well-established package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive: 'fb' is Facebook's npm account, not spam. No deps is expected for core react package. | ai |
Versions (showing 100 of 132)
| Version | Deps | Published |
|---|---|---|
| 19.2.6 | 0 / 0 | |
| 19.2.5 | 0 / 0 | |
| 19.2.4 | 0 / 0 | |
| 19.2.3 | 0 / 0 | |
| 19.2.2 | 0 / 0 | |
| 19.2.1 | 0 / 0 | |
| 19.2.0 | 0 / 0 | |
| 19.1.7 | 0 / 0 | |
| 19.1.6 | 0 / 0 | |
| 19.1.5 | 0 / 0 | |
| 19.1.4 | 0 / 0 | |
| 19.1.3 | 0 / 0 | |
| 19.1.2 | 0 / 0 | |
| 19.1.1 | 0 / 0 | |
| 19.1.0 | 0 / 0 | |
| 19.0.6 | 0 / 0 | |
| 19.0.5 | 0 / 0 | |
| 19.0.4 | 0 / 0 | |
| 19.0.3 | 0 / 0 | |
| 19.0.2 | 0 / 0 | |
| 19.0.1 | 0 / 0 | |
| 19.0.0 | 0 / 0 | |
| 18.3.1 | 1 / 0 | |
| 18.3.0 | 1 / 0 | |
| 18.2.0 | 1 / 0 | |
| 18.1.0 | 1 / 0 | |
| 18.0.0 | 1 / 0 | |
| 17.0.2 | 2 / 0 | |
| 17.0.1 | 2 / 0 | |
| 17.0.0 | 2 / 0 | |
| 16.14.0 | 3 / 0 | |
| 16.13.1 | 3 / 0 | |
| 16.13.0 | 3 / 0 | |
| 16.12.0 | 3 / 0 | |
| 16.11.0 | 3 / 0 | |
| 16.10.2 | 3 / 0 | |
| 16.10.1 | 3 / 0 | |
| 16.10.0 | 3 / 0 | |
| 16.9.0 | 3 / 0 | |
| 16.8.6 | 4 / 0 | |
| 16.8.5 | 4 / 0 | |
| 16.8.4 | 4 / 0 | |
| 16.8.3 | 4 / 0 | |
| 16.8.2 | 4 / 0 | |
| 16.8.1 | 4 / 0 | |
| 16.8.0 | 4 / 0 | |
| 16.7.0 | 4 / 0 | |
| 16.6.3 | 4 / 0 | |
| 16.6.2 | 4 / 0 | |
| 16.6.1 | 4 / 0 | |
| 16.6.0 | 4 / 0 | |
| 16.5.2 | 4 / 0 | |
| 16.5.1 | 4 / 0 | |
| 16.5.0 | 4 / 0 | |
| 16.4.2 | 4 / 0 | |
| 16.4.1 | 4 / 0 | |
| 16.4.0 | 4 / 0 | |
| 16.3.2 | 4 / 0 | |
| 16.3.1 | 4 / 0 | |
| 16.3.0 | 4 / 0 | |
| 16.2.0 | 4 / 0 | |
| 16.1.1 | 4 / 0 | |
| 16.1.0 | 4 / 0 | |
| 16.0.0 | 4 / 0 | |
| 15.7.0 | 5 / 0 | |
| 15.6.2 | 5 / 0 | |
| 15.6.1 | 5 / 0 | |
| 15.6.0 | 5 / 0 | |
| 15.5.4 | 4 / 0 | |
| 15.5.3 | 4 / 0 | |
| 15.5.2 | 4 / 0 | |
| 15.5.1 | 4 / 0 | |
| 15.5.0 | 4 / 0 | |
| 15.4.2 | 3 / 0 | |
| 15.4.1 | 3 / 0 | |
| 15.4.0 | 3 / 0 | |
| 15.3.2 | 3 / 0 | |
| 15.3.1 | 3 / 0 | |
| 15.3.0 | 3 / 0 | |
| 15.2.1 | 3 / 0 | |
| 15.2.0 | 3 / 0 | |
| 15.1.0 | 3 / 0 | |
| 15.0.2 | 3 / 0 | |
| 15.0.1 | 3 / 0 | |
| 15.0.0 | 3 / 0 | |
| 0.14.10 | 2 / 0 | |
| 0.14.9 | 2 / 0 | |
| 0.14.8 | 2 / 0 | |
| 0.14.7 | 2 / 0 | |
| 0.14.6 | 2 / 0 | |
| 0.14.5 | 2 / 0 | |
| 0.14.4 | 2 / 0 | |
| 0.14.3 | 2 / 0 | |
| 0.14.2 | 2 / 0 | |
| 0.14.1 | 2 / 0 | |
| 0.14.0 | 2 / 0 | |
| 0.13.3 | 1 / 0 | |
| 0.13.2 | 1 / 0 | |
| 0.13.1 | 1 / 0 | |
| 0.13.0 | 1 / 0 |
v19.2.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: react-bot.
v19.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: react-bot.
v19.1.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: react-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.6
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: react-bot.
v19.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: react-bot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v19.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v19.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v18.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.