@api-hooks/gh MIT 24 versions

@api-hooks/gh

npm Repository Homepage

React hooks for the GitHub API, built on @tanstack/react-query

24

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

pilmee

Keywords

reacthooksgithubapireact-querytanstack

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped package @api-hooks/gh is a GitHub API hooks library, not a typosquat of got.	ai	2026/04/28
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped package @api-hooks/gh is a GitHub API hooks library, not a typosquat of pg.	ai	2026/04/28
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped package @api-hooks/gh is a GitHub API hooks library, not a typosquat of qs.	ai	2026/04/28

Versions (showing 24 of 24)

Version	Deps	Published
2.3.1	1 / 9	2026-06-02
2.3.0	1 / 9	2026-05-26
2.2.0	1 / 9	2026-05-24
2.1.0	1 / 9	2026-05-23
2.0.0	1 / 9	2026-05-20
1.14.0	1 / 9	2026-05-13
1.13.0	1 / 9	2026-05-12
1.12.0	1 / 10	2026-05-08
1.11.0	1 / 10	2026-05-06
1.10.0	1 / 10	2026-05-04
1.9.0	1 / 10	2026-04-26
1.8.0	1 / 10	2026-04-18
1.7.4	1 / 10	2026-04-18
1.7.3	0 / 10	2026-04-18
1.7.2	0 / 10	2026-04-18
1.7.1	0 / 10	2026-04-18
1.7.0	0 / 10	2026-04-17
1.6.0	0 / 10	2026-04-17
1.5.0	0 / 10	2026-04-17
1.4.0	0 / 9	2026-04-17
1.3.0	0 / 9	2026-04-16
1.2.0	1 / 9	2026-04-16
1.1.0	1 / 9	2026-04-16
1.0.0	1 / 9	2026-04-16

v2.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.14.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.11.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.