@zenstackhq/tanstack-query
TanStack Query Client for consuming ZenStack v3's CRUD service
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 | publisher-changed | AI (provenance): Transition from manual (ymc9) to GitHub Actions CI/CD publishing; backed by SLSA provenance attestation. Stable for this package going forward. | ai | |
| phantom-deps | phantom-dep:decimal.js | AI (phantom-deps): decimal.js is a declared runtime dependency; phantom-dep heuristic false positive for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): ZenStack monorepo refactor; new files are legitimate plugin/runtime code, not injected payloads. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Major version restructuring explains size increase; no obfuscation or malicious patterns detected. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo plugin package; sparse README/keywords is a style choice, not spam. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): semver is a declared runtime dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 3.7.2 | 5 / 20 | |
| 3.7.1 | 5 / 20 | |
| 3.7.0 | 5 / 20 | |
| 3.6.4 | 4 / 21 | |
| 3.6.3 | 4 / 21 | |
| 3.6.2 | 4 / 21 | |
| 3.6.1 | 4 / 21 | |
| 3.6.0 | 4 / 21 | |
| 3.5.6 | 4 / 20 | |
| 3.5.5 | 4 / 20 | |
| 3.5.4 | 4 / 20 | |
| 3.5.3 | 4 / 20 | |
| 3.5.2 | 4 / 20 | |
| 3.5.1 | 4 / 20 | |
| 3.5.0 | 4 / 20 | |
| 3.4.6 | 4 / 20 | |
| 3.4.5 | 4 / 20 | |
| 3.4.4 | 4 / 20 | |
| 3.4.3 | 4 / 20 | |
| 3.4.2 | 4 / 20 | |
| 3.4.1 | 4 / 20 | |
| 3.4.0 | 4 / 20 | |
| 3.3.3 | 4 / 20 | |
| 3.3.2 | 4 / 20 | |
| 3.3.1 | 4 / 20 | |
| 3.3.0 | 4 / 20 | |
| 3.2.1 | 4 / 20 | |
| 3.2.0 | 4 / 20 | |
| 3.1.1 | 4 / 20 | |
| 3.1.0 | 4 / 20 | |
| 3.0.0 | 5 / 17 | |
| 2.22.3 | 6 / 26 | |
| 2.22.2 | 6 / 26 | |
| 2.22.1 | 6 / 26 | |
| 2.22.0 | 6 / 26 | |
| 2.21.1 | 6 / 26 | |
| 2.21.0 | 6 / 26 |
v3.7.2
2 findingsThis version was published by a different npm account than previous versions on 2026-05-31. 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.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.