← Home

@salesforce/kit

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

demianbrechtbyaodferroravi.jayaramappamjrustapapkojleen-sfdccwallsfdhagberg-sfkhawkinsmbettioamphroire-npm-team-userjodarovesfdctakajimjagivarleydbreese-salesforcesalesforce-releasespackagellamaadirasanamjasonschroeder-sfdcdme722jmsjtumobifylwc-adminabirchfieldsfdcsalesforce-admin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:koa AI (typosquat): @salesforce/kit is an official Salesforce scoped package; Levenshtein match to 'koa' is a false positive with no plausible impersonation scenario. ai
typosquat typosquat.levenshtein:vite AI (typosquat): @salesforce/kit is an official Salesforce scoped package; Levenshtein match to 'vite' is a false positive with no plausible impersonation scenario. ai
typosquat typosquat.levenshtein:got AI (typosquat): @salesforce/kit is an official Salesforce scoped package; Levenshtein match to 'got' is a false positive with no plausible impersonation scenario. ai

Versions (showing 3 of 3)

Version Deps Published
3.2.6 1 / 4
3.2.5 1 / 4
3.2.4 1 / 4

v3.2.6

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.

v3.2.5

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.