zustand
🐻 Bear necessities for state management in React
Supply chain provenance
Status for the latest visible version.
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): Published via GitHub Actions with SLSA provenance; missing gitHead is a benign CI config change. | ai | |
| provenance | publisher-changed | AI (provenance): zustand publishes via GitHub Actions CI/CD with SLSA provenance attestation; 'publisher-changed' from daishi to GitHub Actions reflects legitimate automation, not a takeover. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop from v4 to v5 is explained by removal of use-sync-external-store runtime dep and v5 rewrite; not indicative of a stub across this major version boundary. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.0.14 | 0 / 0 | |
| 5.0.13 | 0 / 0 | |
| 5.0.12 | 0 / 0 | |
| 5.0.11 | 0 / 0 | |
| 5.0.10 | 0 / 0 | |
| 5.0.9 | 0 / 0 | |
| 5.0.8 | 0 / 0 | |
| 5.0.7 | 0 / 0 | |
| 5.0.6 | 0 / 0 | |
| 5.0.5 | 0 / 0 | |
| 5.0.4 | 0 / 0 | |
| 4.5.7 | 1 / 0 |
v5.0.14
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: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.11
2 findingsThis version was published by a different npm account than previous versions on 2026-02-01. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.10
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.9
2 findingsThis version was published by a different npm account than previous versions on 2025-11-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.