Is Gk MCP server safe?
- Node.js shell/command execution
- npm install-time lifecycle hook
- Node.js filesystem read
@gitkraken/gk is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 4 risky constructs are reported for review. It can: filesystem read, filesystem write, install time execution and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
@gitkraken/gk 3.1.70
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of Gk MCP server's authors. Report a false positive.
Behavioral traits
How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.
Findings (4)
package.json runs scripts automatically when the package is installed.
"postinstall": "node install.js",
Why it matters: Install scripts are a favorite supply-chain foothold — they execute on every machine that installs the package.
Fix: Inspect the hook command. Install-time scripts are a common supply chain execution vector; ensure they do nothing beyond a documented build step.
The component can run operating-system commands or spawn processes.
import { spawnSync } from "child_process";let result = spawnSync(path.join(binDir, bin), args, {Why it matters: Powerful and often legitimate — confirm the commands aren't built from untrusted input.
Fix: Confirm the command and its arguments are fully controlled and not derived from untrusted input; prefer execFile with an argument array.
The component reads files from disk.
fs.readFileSync(new URL("./package.json", import.meta.url), "utf8"),const zipData = fs.readFileSync(zipPath);
.update(fs.readFileSync(filename))
Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.
Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.
The component writes or deletes files on disk.
fs.rmSync(wrappedDir, { recursive: true, force: true });fs.writeFileSync(file, content);
const writer = fs.createWriteStream(filename);
Why it matters: Usually legitimate, but worth confirming the paths can't be controlled by untrusted input.
Fix: Confirm which files are written/deleted and that paths cannot be influenced by untrusted input.
Check your own component
Run the same evidence-backed scan on any MCP server, agent skill, or package.
Scan your own componentHow we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →