← Home

@quiver-lib/ui

npm

DOM and browser interaction hooks for Quiver

4
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

tessy01

Keywords

reacthooksdomuibrowser

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped package @quiver-lib/ui is a legitimate React hooks library; 'ui' suffix similarity to 'uuid' is purely algorithmic noise, not impersonation. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @quiver-lib/ui has no relation to the 'pg' postgres client; short-string Levenshtein match is a false positive. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @quiver-lib/ui has no relation to 'qs'; short-string Levenshtein match is a false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @quiver-lib/ui has no relation to 'joi'; short-string Levenshtein match is a false positive. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @quiver-lib/ui has no relation to 'yup'; short-string Levenshtein match is a false positive. ai

Versions (showing 4 of 4)

Version Deps Published
1.0.1 0 / 10
1.0.0 0 / 10
0.1.1 0 / 10
0.1.0 0 / 10

v1.0.1

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

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.

v0.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.