← Home

@quiver-lib/ai

npm

AI and ML integration hooks: LLM streaming, speech recognition, on-device inference

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

reacthooksaillmspeechml

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:hapi AI (typosquat): Scoped package @quiver-lib/ai is not a plausible typosquat of 'hapi'; Levenshtein match is a structural false positive on the short /ai suffix. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @quiver-lib/ai is not a plausible typosquat of 'pg'; Levenshtein match is a structural false positive on the short /ai suffix. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @quiver-lib/ai is not a plausible typosquat of 'qs'; Levenshtein match is a structural false positive on the short /ai suffix. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @quiver-lib/ai is not a plausible typosquat of 'joi'; Levenshtein match is a structural false positive on the short /ai suffix. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Scoped package @quiver-lib/ai is not a plausible typosquat of 'ajv'; Levenshtein match is a structural false positive on the short /ai suffix. 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. Consider requesting the maintainer enable provenance via CI/CD.

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.