← Home

@gitkraken/gk

npm Repository Homepage

gk is GitKraken on the command line. It makes working across multiple repos easier with Workspaces, provides access to pull requests and issues from multiple services (GitHub, GitLab, Bitbucket, etc.), and seamlessly connects with GitKraken Client and Git

11
Versions
CC-BY-3.0-US
License
Yes
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

axosoft-dev

Keywords

clicommand-lineefficiencygit-toolproductivityrepository-managementtoolutilityversion-controlmcpgitkraken

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
license uncommon-license:CC-BY-3.0-US AI (license): CC-BY-3.0-US is the stated license for this GitKraken product; stable across versions. ai
semgrep semgrep:child-process-import AI (semgrep): CLI tool legitimately uses child_process; consistent with its documented purpose. ai
install-scripts install-script:postinstall AI (install-scripts): Documented prebuilt-binary fetch pattern with SHA256 checksums per platform in package.json; stable for this CLI package. ai
typosquat typosquat.levenshtein:got AI (typosquat): Scoped package @gitkraken/gk is the official GitKraken CLI, not a typosquat of 'got'. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @gitkraken/gk is the official GitKraken CLI, not a typosquat of 'pg'. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @gitkraken/gk is the official GitKraken CLI, not a typosquat of 'qs'. ai

Versions (showing 11 of 11)

Version Deps Published
3.1.64 3 / 0
3.1.62 3 / 0
3.1.61 3 / 0
3.1.59 3 / 0
3.1.55 3 / 0
3.1.53 4 / 0
3.1.52 4 / 0
3.1.51 4 / 0
3.1.48 4 / 0
3.1.45 4 / 0
3.1.42 4 / 0

v3.1.64

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.62

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.1.61

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.1.59

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.1.55

2 findings
HIGH Package has 'postinstall' script install-scripts

Script: node install.js

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.1.53

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.1.52

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.1.51

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.1.48

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.1.45

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.1.42

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.