@effectify/solid-query
Integration of Effect with TanStack Query for Solid.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Runtime dependency for TypeScript helpers; stable for this package. | ai | |
| phantom-deps | phantom-dep:effect | AI (phantom-deps): Integration wrapper; effect is a peer/config dependency, not direct import. | ai | |
| phantom-deps | phantom-dep:solid-js | AI (phantom-deps): Integration wrapper; solid-js is a peer/config dependency, not direct import. | ai | |
| phantom-deps | phantom-dep:@tanstack/query-core | AI (phantom-deps): Integration wrapper; @tanstack/query-core is a peer/config dependency. | ai | |
| phantom-deps | phantom-dep:@tanstack/solid-query | AI (phantom-deps): Integration wrapper; @tanstack/solid-query is a peer/config dependency. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.5.12 | 1 / 5 | |
| 0.5.11 | 1 / 5 | |
| 0.5.10 | 1 / 5 | |
| 0.5.9 | 1 / 5 | |
| 0.5.8 | 1 / 5 | |
| 0.5.7 | 1 / 5 | |
| 0.5.6 | 1 / 5 | |
| 0.5.5 | 1 / 5 | |
| 0.5.4 | 1 / 5 | |
| 0.5.3 | 5 / 1 | |
| 0.5.2 | 5 / 1 | |
| 0.5.1 | 5 / 1 | |
| 0.5.0 | 5 / 1 | |
| 0.4.7 | 5 / 1 | |
| 0.4.6 | 5 / 1 | |
| 0.4.5 | 5 / 1 | |
| 0.3.1 | 5 / 1 | |
| 0.0.3 | 5 / 1 | |
| 0.0.1 | 1 / 1 |
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.