@trackunit/react-graphql-tools
This tool allows you to generate React Hooks for your GraphQL files. Just add this executor to the project with *.graphql files, then it creates React hooks.
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): 589-version org package; no material changes in this release; dormancy pattern consistent with org publishing cadence. | ai | |
| dependencies | unvetted-dep:win-ca | AI (dependencies): win-ca is a legitimate Windows CA certificate utility; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@graphql-codegen/client-preset | AI (phantom-deps): Used in codegen config files, not directly imported in source — expected pattern for codegen tooling. | ai |
Versions (showing 51 of 351)
| Version | Deps | Published |
|---|---|---|
| 1.14.15 | 8 / 0 | |
| 1.14.14 | 8 / 0 | |
| 1.14.13 | 8 / 0 | |
| 1.14.12 | 8 / 0 | |
| 1.14.11 | 8 / 0 | |
| 1.14.10 | 8 / 0 | |
| 1.14.9 | 8 / 0 | |
| 1.14.8 | 8 / 0 | |
| 1.14.7 | 8 / 0 | |
| 1.14.6 | 8 / 0 | |
| 1.14.4 | 8 / 0 | |
| 1.14.3 | 8 / 0 | |
| 1.14.2 | 8 / 0 | |
| 1.14.1 | 8 / 0 | |
| 1.14.0 | 8 / 0 | |
| 1.13.6 | 8 / 0 | |
| 1.13.5 | 8 / 0 | |
| 1.13.4 | 8 / 0 | |
| 1.13.3 | 8 / 0 | |
| 1.13.2 | 8 / 0 | |
| 1.13.1 | 8 / 0 | |
| 1.12.44 | 8 / 0 | |
| 1.12.43 | 8 / 0 | |
| 1.12.42 | 8 / 0 | |
| 1.12.41 | 8 / 0 | |
| 1.12.40 | 8 / 0 | |
| 1.12.39 | 8 / 0 | |
| 1.12.37 | 8 / 0 | |
| 1.12.36 | 8 / 0 | |
| 1.12.35 | 8 / 0 | |
| 1.12.34 | 8 / 0 | |
| 1.12.32 | 8 / 0 | |
| 1.12.30 | 8 / 0 | |
| 1.12.29 | 8 / 0 | |
| 1.12.28 | 8 / 0 | |
| 1.12.27 | 8 / 0 | |
| 1.12.26 | 8 / 0 | |
| 1.12.25 | 8 / 0 | |
| 1.12.24 | 8 / 0 | |
| 1.12.23 | 8 / 0 | |
| 1.12.22 | 8 / 0 | |
| 1.12.21 | 8 / 0 | |
| 1.12.19 | 8 / 0 | |
| 1.12.18 | 8 / 0 | |
| 1.12.17 | 8 / 0 | |
| 1.12.15 | 8 / 0 | |
| 1.12.14 | 8 / 0 | |
| 1.12.13 | 8 / 0 | |
| 1.12.12 | 8 / 0 | |
| 1.12.11 | 8 / 0 | |
| 1.12.10 | 8 / 0 |
v1.14.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.