@api-hooks/osv
React hooks for the OSV (Open Source Vulnerabilities) API, built on @tanstack/react-query
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Small utility package; lack of Sigstore attestation is not a disqualifier given otherwise clean signals. | ai | |
| phantom-deps | phantom-dep:osv-api-client | AI (phantom-deps): osv-api-client is a declared runtime dep; bundled output via vite likely inlines it, explaining no direct import in source. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @api-hooks/osv; clearly not a typosquat of qs — different namespace, purpose, and audience. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped package @api-hooks/osv; clearly not a typosquat of ajv — different namespace, purpose, and audience. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.7.0 | 1 / 9 | |
| 1.6.0 | 1 / 9 | |
| 1.5.0 | 1 / 9 | |
| 1.4.0 | 1 / 9 | |
| 1.3.1 | 1 / 9 | |
| 1.3.0 | 1 / 9 | |
| 1.2.0 | 1 / 9 | |
| 1.1.0 | 1 / 9 | |
| 1.0.4 | 1 / 9 | |
| 1.0.3 | 1 / 9 | |
| 1.0.2 | 1 / 9 | |
| 1.0.1 | 1 / 9 | |
| 1.0.0 | 1 / 9 |
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.