@tanstack/vue-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@tanstack/match-sorter-utils | AI (dependencies): First-party TanStack package; stable false positive for this ecosystem. | ai |
Versions (showing 95 of 295)
| Version | Deps | Published |
|---|---|---|
| 5.44.0 | 4 / 5 | |
| 5.41.0 | 4 / 5 | |
| 5.40.1 | 4 / 5 | |
| 5.40.0 | 4 / 5 | |
| 5.38.0 | 4 / 5 | |
| 5.37.1 | 4 / 5 | |
| 5.36.1 | 4 / 5 | |
| 5.36.0 | 4 / 5 | |
| 5.35.5 | 4 / 5 | |
| 5.35.4 | 4 / 5 | |
| 5.35.2 | 4 / 5 | |
| 5.35.1 | 4 / 5 | |
| 5.34.2 | 4 / 5 | |
| 5.34.1 | 4 / 5 | |
| 5.32.1 | 4 / 5 | |
| 5.32.0 | 4 / 5 | |
| 5.31.0 | 4 / 5 | |
| 5.29.0 | 4 / 5 | |
| 5.28.13 | 4 / 5 | |
| 5.28.12 | 4 / 5 | |
| 5.28.9 | 4 / 5 | |
| 5.28.8 | 4 / 5 | |
| 5.28.7 | 4 / 5 | |
| 5.28.6 | 4 / 5 | |
| 5.28.4 | 4 / 5 | |
| 5.28.2 | 4 / 5 | |
| 5.28.1 | 4 / 5 | |
| 5.28.0 | 4 / 5 | |
| 5.27.5 | 4 / 5 | |
| 5.27.4 | 4 / 5 | |
| 5.27.3 | 4 / 5 | |
| 5.27.1 | 4 / 5 | |
| 5.26.3 | 4 / 5 | |
| 5.25.0 | 4 / 5 | |
| 5.24.8 | 4 / 5 | |
| 5.24.7 | 4 / 5 | |
| 5.24.6 | 4 / 5 | |
| 5.24.5 | 4 / 5 | |
| 5.24.2 | 4 / 5 | |
| 5.24.1 | 4 / 5 | |
| 5.22.2 | 4 / 5 | |
| 5.21.7 | 4 / 5 | |
| 5.21.4 | 4 / 5 | |
| 5.21.2 | 4 / 5 | |
| 5.20.5 | 4 / 5 | |
| 5.20.4 | 4 / 5 | |
| 5.20.2 | 4 / 5 | |
| 5.20.1 | 4 / 5 | |
| 5.18.1 | 4 / 5 | |
| 5.18.0 | 4 / 5 | |
| 5.17.19 | 4 / 5 | |
| 5.17.15 | 4 / 5 | |
| 5.17.14 | 4 / 5 | |
| 5.17.13 | 4 / 5 | |
| 5.17.12 | 4 / 5 | |
| 5.17.11 | 4 / 5 | |
| 5.17.10 | 4 / 5 | |
| 5.17.9 | 4 / 5 | |
| 5.17.8 | 4 / 5 | |
| 5.17.7 | 4 / 5 | |
| 5.17.4 | 4 / 5 | |
| 5.17.3 | 4 / 5 | |
| 5.17.2 | 4 / 5 | |
| 5.17.1 | 4 / 5 | |
| 5.17.0 | 4 / 5 | |
| 5.15.5 | 4 / 5 | |
| 5.15.4 | 4 / 5 | |
| 5.15.3 | 4 / 5 | |
| 5.15.0 | 4 / 4 | |
| 5.14.6 | 4 / 4 | |
| 5.14.4 | 4 / 4 | |
| 5.14.3 | 4 / 4 | |
| 5.14.2 | 4 / 4 | |
| 5.14.1 | 4 / 4 | |
| 5.14.0 | 4 / 4 | |
| 5.13.4 | 4 / 4 | |
| 5.12.2 | 4 / 4 | |
| 5.12.1 | 4 / 4 | |
| 5.12.0 | 4 / 4 | |
| 5.10.0 | 4 / 4 | |
| 5.9.0 | 4 / 4 | |
| 5.8.7 | 4 / 4 | |
| 5.8.6 | 4 / 4 | |
| 5.8.4 | 4 / 4 | |
| 5.8.3 | 4 / 4 | |
| 5.8.1 | 4 / 4 | |
| 5.7.3 | 4 / 4 | |
| 5.7.2 | 4 / 4 | |
| 5.4.3 | 4 / 4 | |
| 5.4.1 | 4 / 4 | |
| 5.4.0 | 4 / 4 | |
| 5.0.5 | 4 / 4 | |
| 5.0.4 | 4 / 4 | |
| 5.0.0 | 4 / 4 | |
| 4.44.0 | 4 / 3 |
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.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.7
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.1
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.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.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.17.12
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.2
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.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.14.3
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.2
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.9.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.4
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.3
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.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
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.4
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.