@tanstack/query-sync-storage-persister
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transition to GitHub Actions CI/CD publishing with SLSA provenance attestation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known TanStack collaborators added; consistent with active project maintenance. | ai | |
| dependencies | unvetted-dep:@tanstack/query-persist-client-core | AI (dependencies): First-party TanStack sibling package pinned to same version; stable false positive for this package. | ai |
Versions (showing 4 of 104)
| Version | Deps | Published |
|---|---|---|
| 5.74.7 | 2 / 1 | |
| 4.44.0 | 1 / 0 | |
| 4.43.0 | 1 / 0 | |
| 4.41.1 | 1 / 0 |
v5.74.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.44.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.43.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-28. 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.
v4.41.1
2 findingsThis version was published by a different npm account than previous versions on 2026-01-18. 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.