← Home

react-redux

npm Repository Homepage

Official React bindings for Redux

3
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

gaearontimdorrphryneasacemarkeeskimojo

Keywords

reactreactjsredux

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from maintainer to GitHub Actions CI/CD publishing with SLSA provenance; expected for this project. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects normal release cadence for a stable, mature package; CI migration explains the gap. ai
dependencies unvetted-dep:use-sync-external-store AI (dependencies): use-sync-external-store is a well-known React ecosystem package; react-redux has depended on it for concurrent React support across multiple versions. ai
dependencies unvetted-dep:@types/use-sync-external-store AI (dependencies): Type definitions package for use-sync-external-store; a stable, benign dependency for this package. ai
phantom-deps phantom-dep:@types/use-sync-external-store AI (phantom-deps): Type-only package loaded by convention, not directly imported. Expected pattern for @types/* packages in TypeScript projects. ai

Versions (showing 3 of 3)

Version Deps Published
9.3.0 2 / 27
9.2.0 2 / 27
7.2.8 6 / 38

v9.3.0

2 findings
HIGH Publisher changed: acemarke → GitHub Actions (on 2026-05-15) provenance

This version was published by a different npm account than previous versions on 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v7.2.8

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.