@salesforce/kit
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Trusted publisher, no code/behavior change; likely internal team roster update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with legitimate maintainer roster churn, not takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived official package with clean diff; dormancy likely reflects historical version import, not new risk. | ai | |
| 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 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.2.6 | 1 / 4 | |
| 3.2.5 | 1 / 4 | |
| 3.2.4 | 1 / 4 | |
| 3.2.3 | 1 / 4 | |
| 3.2.2 | 1 / 4 | |
| 3.2.1 | 1 / 4 | |
| 3.2.0 | 1 / 4 | |
| 3.1.6 | 1 / 4 | |
| 3.1.5 | 2 / 4 | |
| 3.1.4 | 2 / 4 | |
| 3.1.3 | 2 / 4 | |
| 3.1.2 | 2 / 4 | |
| 3.1.1 | 2 / 4 | |
| 3.1.0 | 2 / 4 | |
| 3.0.15 | 2 / 25 | |
| 3.0.14 | 2 / 25 | |
| 3.0.13 | 2 / 25 | |
| 3.0.12 | 2 / 25 | |
| 3.0.11 | 2 / 25 | |
| 3.0.10 | 2 / 25 | |
| 3.0.9 | 2 / 25 | |
| 3.0.8 | 2 / 25 | |
| 3.0.7 | 2 / 25 | |
| 3.0.6 | 2 / 25 | |
| 3.0.5 | 2 / 25 | |
| 3.0.4 | 2 / 25 | |
| 3.0.3 | 2 / 25 | |
| 3.0.2 | 2 / 25 | |
| 3.0.1 | 2 / 25 | |
| 3.0.0 | 2 / 25 |
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.