SkillTotal

Is Packmind MCP server safe?

Some risk - review before installing
Notable — review in context (capabilities are not malware):
  • Python shell/command execution
  • Node.js shell/command execution
  • Possible command injection (exec with dynamic command)

packmind is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 13 risky constructs are reported for review. It can: dynamic code execution, filesystem read, filesystem write, install time execution, mcp tools detected, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 30/100 (medium).

packmind 1.16.2

npm_package · https://github.com/PackmindHub/packmind
MEDIUM
30
/ 100 risk score
Snapshot · scanned Aug 15, 2026 · packmind@1.16.2 · engine 0.38.1 / ruleset 42

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of Packmind MCP server's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
dynamic code executionfilesystem readfilesystem writeinstall time executionmcp tools detectednetwork egressshell execution

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Tool surface
Tool Usage
Execution authority
Tool Access Control / Direct Tool Access
Filesystem reach
Tool Execution Context
Network egress
Interaction & Communication / Direct Communication
Network exposure
Interaction & Communication
Supply-chain provenance risk
General Protections / Supply Chain

Findings (13)

HIGHPossible command injection (exec with dynamic command)ST-CMDI-NODE

The code builds an OS command out of values that can change at runtime, then runs it through a shell.

execSync(`${whichCommand} ${command}`, { stdio: 'pipe' });
const stdout = execSync(`git ${cmd}`, {
execSync(`npm install -g ${NPM_PACKAGE}@${version}`, {

Why it matters: If any of those values come from untrusted input, an attacker can run their own commands on the machine.

Fix: Use execFile/spawn with an argument array instead of exec; never build a shell command string from external input.

HIGHNode.js dynamic code executionST-DYN-NODE

The code turns strings into live code at runtime (eval / new Function / exec).

Why it matters: If those strings aren't fixed and trusted, they become a way to run arbitrary code.

Fix: Avoid evaluating dynamically constructed code; if unavoidable, ensure the input is a trusted constant and never derived from external data.

HIGHMCP server launches a host commandST-MCP-SERVER-EXEC

An MCP server entry launches a command on your host.

Why it matters: Trusting the manifest means running that binary — verify what it is and where it comes from.

Fix: Verify the launched command and its source before trusting this MCP server configuration.

HIGHNode.js shell/command executionST-SHELL-NODE

The component can run operating-system commands or spawn processes.

const match = CLI_USER_AGENT_REGEX.exec(userAgent);
const embedResult = await Bun.spawn(['bun', 'run', embedWasmScript], {
const compileResult = await Bun.spawn(

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.

HIGHPython shell/command executionST-SHELL-PY

The component can run operating-system commands or spawn processes.

result = subprocess.run(
                ["git", "-C", cwd, "symbolic-ref", "--short", "HEAD"],
                capture_output=True, text=True, timeout=2
            )

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; avoid shell=True.

MEDIUMServer bound to all network interfacesST-EXPOSE-BIND

A server is bound to all network interfaces (0.0.0.0), not just your own machine.

host: process.env.NX_WATCHER ? '0.0.0.0' : 'localhost',

Why it matters: Without authentication, other hosts on the network can reach it.

Fix: Bind to 127.0.0.1 for local-only use, or require authentication and restrict access if remote exposure is intended.

MEDIUMNode.js filesystem readST-FS-NODE-READ

The component reads files from disk.

const packageJsonContent = fs.readFileSync(packageJsonPath, 'utf-8');
let content = fs.readFileSync(mainCjsPath, 'utf8');
const packageJson = JSON.parse(fs.readFileSync(packageJsonPath, 'utf8'));
const mainContent = fs.readFileSync(mainCjsPath, 'utf8');
return await fs.readFile(filePath, 'utf-8');
content = await fs.readFile(filePath, 'utf-8');
const existingContent = await fs.readFile(fullPath, 'utf-8');
const existingContent = await fs.readFile(fullPath, 'utf-8');
currentContent = await fs.readFile(fullPath, 'utf-8');
const existingContent = await fs.readFile(fullPath, 'utf-8');
currentContent = await fs.readFile(fullPath, 'utf-8');
const actual = await fs.readFile(fullPath);
const actual = await fs.readFile(fullPath, 'utf-8');
const content = fs.readFileSync(lockFilePath, 'utf-8');
const configContent = await fs.readFile(configPath, 'utf-8');
const content = await fs.readFile(lockFilePath, 'utf-8');
const content = fs.readFileSync(this.storagePath, 'utf-8');
const content = fs.readFileSync(credentialsPath, 'utf-8');

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.

MEDIUMNode.js filesystem write/deleteST-FS-NODE-WRITE

The component writes or deletes files on disk.

fs.writeFileSync(mainCjsPath, content);
fs.writeFileSync(packageJsonPath, JSON.stringify(packageJson, null, 2) + '\n');
fs.writeFileSync(mainCjsPath, '#!/usr/bin/env node\n' + mainContent);
fs.writeFileSync(path.join(moduleDir, 'index.js'), stubContent.trim());

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.

MEDIUMPython filesystem readST-FS-PY-READ

The component reads files from disk.

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.

MEDIUMPython filesystem write/deleteST-FS-PY-WRITE

The component writes or deletes files on disk.

example_script.write_text(EXAMPLE_SCRIPT.format(skill_name=skill_name))
example_reference.write_text(EXAMPLE_REFERENCE.format(skill_title=skill_title))

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.

MEDIUMnpm prepare hookST-INSTALL-NPM-PREPARE

package.json has a 'prepare' script (runs on git/local installs and before publishing).

"prepare": "node scripts/prepare.mjs",

Why it matters: Usually a build step, but confirm it doesn't fetch or run remote code.

Fix: Usually a legitimate build step; confirm it only builds and does not fetch or execute remote code.

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.

Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.

LOWMCP tool surface detectedST-MCP-DETECTED

An MCP tool surface (manifest or tool definitions) was found.

Why it matters: Just context — review which tools it offers and their permissions.

Fix: Review the declared MCP tools and their permissions.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →