@powersync/tanstack-react-query
PowerSync integration with TanStack Query for offline-first and real-time data synchronization in React apps
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 | slsa-provenance | AI (provenance): Published via CI/CD with Sigstore attestation; stable supply chain signal for this package. | ai |
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 0.3.0 | 3 / 6 | |
| 0.2.15 | 3 / 6 | |
| 0.2.14 | 3 / 6 | |
| 0.2.13 | 3 / 6 | |
| 0.2.12 | 3 / 6 | |
| 0.2.11 | 3 / 6 | |
| 0.2.10 | 3 / 6 | |
| 0.2.9 | 3 / 6 | |
| 0.2.8 | 3 / 6 | |
| 0.2.7 | 3 / 6 | |
| 0.2.6 | 3 / 6 | |
| 0.2.5 | 3 / 6 | |
| 0.1.14 | 3 / 5 | |
| 0.1.13 | 3 / 4 | |
| 0.1.12 | 3 / 4 | |
| 0.1.11 | 3 / 4 | |
| 0.1.10 | 3 / 4 | |
| 0.1.9 | 3 / 4 | |
| 0.1.8 | 3 / 4 | |
| 0.1.7 | 3 / 4 | |
| 0.1.6 | 3 / 4 | |
| 0.1.5 | 3 / 4 | |
| 0.1.4 | 3 / 4 | |
| 0.1.3 | 3 / 4 | |
| 0.1.2 | 3 / 4 | |
| 0.1.1 | 3 / 4 | |
| 0.1.0 | 3 / 4 | |
| 0.0.31 | 3 / 4 | |
| 0.0.30 | 3 / 4 | |
| 0.0.29 | 3 / 4 | |
| 0.0.28 | 3 / 4 | |
| 0.0.27 | 3 / 4 | |
| 0.0.26 | 3 / 4 | |
| 0.0.25 | 3 / 4 | |
| 0.0.24 | 3 / 4 | |
| 0.0.23 | 3 / 4 | |
| 0.0.22 | 3 / 4 | |
| 0.0.21 | 3 / 4 | |
| 0.0.20 | 3 / 4 | |
| 0.0.19 | 3 / 4 | |
| 0.0.18 | 3 / 4 | |
| 0.0.17 | 3 / 4 | |
| 0.0.16 | 3 / 4 | |
| 0.0.15 | 3 / 4 | |
| 0.0.14 | 3 / 5 | |
| 0.0.13 | 3 / 5 | |
| 0.0.12 | 3 / 5 | |
| 0.0.11 | 3 / 5 | |
| 0.0.10 | 3 / 5 | |
| 0.0.9 | 3 / 5 | |
| 0.0.8 | 3 / 4 |
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.