@gitkraken/core-gitlens
GitLens core — shared Git / AI / GitHub primitives for internal GitKraken consumption
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env for git subprocess execution is standard and expected in a git CLI wrapper. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Utility encoding helpers in a git tool; no payload hiding. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Utility encoding helper; no payload hiding. | ai |
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gitkraken/vscode-gitlens/blob/5e72fd066f876816f544b17b772f6d8669d1e323/src/git-cli/exec/git.ts#L539 537 | */ 538 | private getBaseEnv(): Record<string, string | undefined> { > 539 | return (this._baseEnv ??= { 540 | ...process.env, 541 | ...(this.options.env ?? emptyObj),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/gitkraken/vscode-gitlens/blob/e8509df14b56a40e112fa18a1ab03bdf73ea8a1e/src/git-cli/exec/git.ts#L487 485 | */ 486 | private getBaseEnv(): Record<string, string | undefined> { > 487 | return (this._baseEnv ??= { 488 | ...process.env, 489 | ...(this.options.env ?? emptyObj),
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.