@tanstack/query-async-storage-persister
A persister for asynchronous storages, to be used with TanStack/Query
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): Transition from personal account to GitHub Actions CI/CD; SLSA provenance confirms legitimate automation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): schiller-manuel and lachlancollins are known TanStack Query contributors. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Sub-package of TanStack Query monorepo; publish cadence varies per package within the repo. | ai |
Versions (showing 71 of 271)
| Version | Deps | Published |
|---|---|---|
| 5.35.1 | 1 / 0 | |
| 5.34.2 | 1 / 0 | |
| 5.34.1 | 1 / 0 | |
| 5.32.1 | 1 / 0 | |
| 5.32.0 | 1 / 0 | |
| 5.31.0 | 1 / 0 | |
| 5.29.1 | 1 / 0 | |
| 5.29.0 | 1 / 0 | |
| 5.28.13 | 1 / 0 | |
| 5.28.12 | 1 / 0 | |
| 5.28.9 | 1 / 0 | |
| 5.28.8 | 1 / 0 | |
| 5.28.6 | 1 / 0 | |
| 5.28.4 | 1 / 0 | |
| 5.28.2 | 1 / 0 | |
| 5.28.0 | 1 / 0 | |
| 5.27.5 | 1 / 0 | |
| 5.27.4 | 1 / 0 | |
| 5.27.3 | 1 / 0 | |
| 5.27.1 | 1 / 0 | |
| 5.26.3 | 1 / 0 | |
| 5.25.0 | 1 / 0 | |
| 5.24.8 | 1 / 0 | |
| 5.24.7 | 1 / 0 | |
| 5.24.6 | 1 / 0 | |
| 5.24.5 | 1 / 0 | |
| 5.24.2 | 1 / 0 | |
| 5.24.1 | 1 / 0 | |
| 5.22.2 | 1 / 0 | |
| 5.21.7 | 1 / 0 | |
| 5.21.4 | 1 / 0 | |
| 5.21.2 | 1 / 0 | |
| 5.20.5 | 1 / 0 | |
| 5.20.4 | 1 / 0 | |
| 5.20.2 | 1 / 0 | |
| 5.20.1 | 1 / 0 | |
| 5.19.1 | 1 / 0 | |
| 5.18.1 | 1 / 0 | |
| 5.18.0 | 1 / 0 | |
| 5.17.19 | 1 / 0 | |
| 5.17.15 | 1 / 0 | |
| 5.17.14 | 1 / 0 | |
| 5.17.11 | 1 / 0 | |
| 5.17.10 | 1 / 0 | |
| 5.17.9 | 1 / 0 | |
| 5.17.8 | 1 / 0 | |
| 5.17.7 | 1 / 0 | |
| 5.17.4 | 1 / 0 | |
| 5.17.3 | 1 / 0 | |
| 5.17.1 | 1 / 0 | |
| 5.17.0 | 1 / 0 | |
| 5.15.5 | 1 / 0 | |
| 5.15.4 | 1 / 0 | |
| 5.14.2 | 1 / 0 | |
| 5.14.1 | 1 / 0 | |
| 5.14.0 | 1 / 0 | |
| 5.13.4 | 1 / 0 | |
| 5.12.1 | 1 / 0 | |
| 5.12.0 | 1 / 0 | |
| 5.10.0 | 1 / 0 | |
| 5.8.7 | 1 / 0 | |
| 5.8.6 | 1 / 0 | |
| 5.8.3 | 1 / 0 | |
| 5.8.1 | 1 / 0 | |
| 5.7.2 | 1 / 0 | |
| 5.4.3 | 1 / 0 | |
| 5.0.5 | 1 / 0 | |
| 5.0.0 | 1 / 0 | |
| 4.44.0 | 1 / 0 | |
| 4.43.0 | 1 / 0 | |
| 4.41.1 | 1 / 0 |
v5.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.