SkillTotal

Is @claude-flow/embeddings safe?

No malicious indicators - review capabilities before installing
Notable — review in context (capabilities are not malware):
  • Node.js shell/command execution
  • Node.js network egress

@claude-flow/embeddings is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 2 risky constructs are reported for review. It can: network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

@claude-flow/embeddings 3.0.0-alpha.45

npm_package · npm:@claude-flow/embeddings
LOW
0
/ 100 risk score
Snapshot · scanned Sep 27, 2026 · @claude-flow/embeddings@3.0.0-alpha.45 · engine 0.53.0 / ruleset 60

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of @claude-flow/embeddings's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
network egressshell execution

Behavioral traits

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

Execution authority
Tool Access Control / Direct Tool Access
Network egress
Interaction & Communication / Direct Communication

Findings (2)

HIGHNode.js shell/command executionST-SHELL-NODE

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

import { spawn } from 'node:child_process';
proc = spawn(bin, args, { stdio: ['ignore', 'pipe', 'pipe'] });
import { spawn, type ChildProcessByStdio } from 'node:child_process';
proc = spawn(bin, args, { stdio: ['ignore', 'pipe', 'pipe'] }) as ChildProcessByStdio<null, Readable, Readable>;

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.

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

const response = await fetch(this.baseURL, {
const response = await fetch(this.baseURL, {

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.

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 →