@react-hook/latest
4
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
jaredlunde
Keywords
reactreact componentuse-refuse-latestuse-effect-callbackuseeffect callback
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:vitest | AI (typosquat): @react-hook/latest is a scoped React hook package with no relation to vitest; the Levenshtein match is a false positive across completely unrelated packages in different namespaces. | ai | |
| provenance | no-provenance | AI (provenance): Package is nearly 6 years old, predating widespread Sigstore provenance adoption. No provenance is expected and not a risk signal here. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.3 | 0 / 19 | |
| 1.0.2 | 0 / 19 | |
| 1.0.1 | 0 / 19 | |
| 1.0.0 | 0 / 19 |
v1.0.2
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.