@ahooksjs/use-request
React Hooks for fetching, caching and updating asynchronous data
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 |
|---|---|---|---|---|
| typosquat | typosquat.pattern:request | AI (typosquat): @ahooksjs/use-request is the official Alibaba ahooks data-fetching hook; 'use-request' follows React hook naming conventions and is not impersonating the 'request' package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from fan576679268 to tli4 in 2020 is a legitimate maintainer transition within the Alibaba/ahooks project. tli4 has a long track record and the package content is unchanged. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance attestation; no-provenance is expected for this era of publishing and not a risk signal here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.8.15 | 2 / 2 | |
| 2.8.14 | 2 / 2 | |
| 2.8.13 | 2 / 2 | |
| 2.8.12 | 2 / 2 | |
| 2.8.11 | 3 / 2 | |
| 2.8.10 | 2 / 2 | |
| 2.8.9 | 2 / 2 | |
| 2.8.8 | 2 / 2 | |
| 2.8.7 | 2 / 2 | |
| 2.8.6 | 2 / 2 | |
| 2.8.5 | 2 / 2 | |
| 2.8.4 | 2 / 2 | |
| 2.8.3 | 2 / 2 | |
| 2.8.2 | 2 / 2 | |
| 2.8.1 | 2 / 2 | |
| 2.8.0 | 2 / 2 | |
| 2.7.0 | 2 / 2 | |
| 2.6.0 | 2 / 2 | |
| 2.5.0 | 2 / 2 | |
| 2.4.0 | 2 / 2 | |
| 2.3.0 | 2 / 2 | |
| 2.2.0 | 2 / 2 | |
| 2.0.2 | 2 / 2 | |
| 2.0.1 | 2 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 3 |
v2.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-03-19. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2021-02-01. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-11-03. This could indicate a legitimate maintainer transition or an account compromise.
v2.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-10-30. This could indicate a legitimate maintainer transition or an account compromise.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-14. This could indicate a legitimate maintainer transition or an account compromise.
v2.4.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v2.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-07-23. This could indicate a legitimate maintainer transition or an account compromise.
v2.2.0
2 findingsThis version was published by a different npm account than previous versions on 2020-07-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2020-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-06-12. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.0
2 findingsPackage name '@ahooksjs/use-request' matches a known typosquatting pattern (hyphen swap, prefix/suffix) of 'request'.
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.