ahooks
react hooks library
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @types/js-cookie is a pure TypeScript type definitions package for js-cookie, which was already a dependency. Adding types alongside an existing dep is benign and routine. | ai | |
| provenance | publisher-changed | AI (provenance): The awmleer→taoweng transition is a documented maintainer handoff within the Alibaba/ahooks team; taoweng has a long, clean track record on npm. | ai | |
| dependencies | unvetted-dep:ahooks-v3-count | AI (dependencies): ahooks-v3-count is the ahooks team's own telemetry/adoption-counting package; its presence is a known, intentional pattern for this library. | ai | |
| phantom-deps | phantom-dep:ahooks-v3-count | AI (phantom-deps): Declared but not directly imported; consistent with indirect/config-level usage by the ahooks telemetry mechanism. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() inside a Proxy handler is idiomatic JS for reactive proxy implementation (useReactive hook). Not obfuscation; pattern is stable across versions of this package. | ai | |
| phantom-deps | phantom-dep:@types/js-cookie | AI (phantom-deps): @types/js-cookie is intentionally bundled as a runtime dep for type definitions. Minor packaging quirk, not a security issue; stable for this package. | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 3.9.7 | 10 / 0 | |
| 3.9.6 | 10 / 0 | |
| 3.9.5 | 10 / 1 | |
| 3.9.4 | 9 / 1 | |
| 3.9.3 | 9 / 1 | |
| 3.9.2 | 9 / 0 | |
| 3.9.1 | 9 / 0 | |
| 3.9.0 | 9 / 13 | |
| 3.8.5 | 9 / 9 | |
| 3.8.4 | 9 / 9 | |
| 3.8.3 | 9 / 9 | |
| 3.8.2 | 9 / 9 | |
| 3.8.1 | 9 / 9 | |
| 3.8.0 | 9 / 9 | |
| 3.7.11 | 9 / 9 | |
| 3.7.10 | 8 / 9 | |
| 3.7.9 | 8 / 9 | |
| 3.7.8 | 10 / 10 | |
| 3.7.7 | 10 / 10 | |
| 3.7.6 | 10 / 10 | |
| 3.7.5 | 9 / 9 | |
| 3.7.4 | 9 / 9 | |
| 3.7.3 | 8 / 9 | |
| 3.7.2 | 8 / 9 | |
| 3.7.1 | 8 / 9 | |
| 3.7.0 | 8 / 9 | |
| 3.6.2 | 8 / 9 | |
| 3.5.2 | 8 / 9 | |
| 3.5.1 | 8 / 9 | |
| 3.5.0 | 8 / 9 | |
| 3.4.1 | 8 / 9 | |
| 3.4.0 | 8 / 9 | |
| 3.3.13 | 8 / 9 | |
| 3.3.12 | 8 / 9 | |
| 3.3.11 | 8 / 9 | |
| 3.3.10 | 8 / 9 | |
| 3.3.9 | 8 / 9 | |
| 3.3.8 | 8 / 9 | |
| 3.3.0 | 8 / 9 | |
| 3.2.0 | 8 / 9 | |
| 3.1.14 | 8 / 9 | |
| 3.1.13 | 8 / 9 | |
| 3.1.12 | 8 / 9 | |
| 3.1.11 | 8 / 9 | |
| 3.1.10 | 8 / 9 | |
| 3.1.9 | 8 / 9 | |
| 3.1.8 | 7 / 10 | |
| 3.1.7 | 7 / 10 | |
| 3.1.6 | 7 / 10 | |
| 3.1.5 | 7 / 10 | |
| 3.1.4 | 7 / 10 |
v3.9.7
2 findingsThis version was published by a different npm account than previous versions on 2026-03-23. 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.
v3.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.11
2 findingsPackage 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 2024-04-01. This could indicate a legitimate maintainer transition or an account compromise.
v3.7.10
2 findingsPackage 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 2024-02-01. This could indicate a legitimate maintainer transition or an account compromise.
v3.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
2 findingsThis version was published by a different npm account than previous versions on 2022-06-29. 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.
v3.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (awmleer) than the most recent previously approved version (fan576679268) on 2022-06-16, but awmleer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.