← Home

react-refresh

npm Repository Homepage

React is a JavaScript library for building user interfaces.

4
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

react-bot

Keywords

react

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): React team migrated all packages to react-bot publisher; legitimate org-wide transition. ai
provenance publisher-changed AI (provenance): Publisher change from gnoff to react-bot is the known React team bot migration. ai
maintainer-change maintainer-added AI (maintainer-change): react-bot is the React team's official publishing bot. ai
maintainer-change maintainer-removed AI (maintainer-change): Previous individual maintainers replaced by react-bot per React team policy. ai

Versions (showing 4 of 4)

Version Deps Published
0.18.0 0 / 3
0.17.0 0 / 3
0.16.0 0 / 3
0.14.0 0 / 3

v0.17.0

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (sebmarkbage, necolas, gaearon, threepointone, acdlite, brianvaughn, gnoff, trueadm, lunaruan) were replaced by new maintainers (react-bot). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: gnoff → react-bot (on 2025-03-28) provenance

This version was published by a different npm account than previous versions on 2025-03-28. 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.

v0.16.0

2 findings
HIGH Publisher changed: gnoff → react-bot (on 2024-12-05) provenance

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

v0.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.