← Home

@vercel/kv

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

Maintainers

snokohnmatt.strakaijjkquietshuvercel-release-botnick.traceymatheusschriswdmrzeit-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): @vercel/kv is a legitimate scoped Vercel package, not a typosquat of koa. ai
typosquat typosquat.levenshtein:pg AI (typosquat): @vercel/kv is a legitimate scoped Vercel package, not a typosquat of pg. ai
typosquat typosquat.levenshtein:qs AI (typosquat): @vercel/kv is a legitimate scoped Vercel package, not a typosquat of qs. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): @vercel/kv is a legitimate scoped Vercel package, not a typosquat of ajv. ai

Versions (showing 1 of 1)

Version Deps Published
3.0.0 1 / 15

v3.0.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.