Is @promptbook/remote-client safe?
- Node.js shell/command execution
- Node.js dynamic code execution
@promptbook/remote-client 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: dynamic code execution and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
@promptbook/remote-client 0.114.0-41
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of @promptbook/remote-client'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 (2)
The code turns strings into live code at runtime (eval / new Function / exec).
eval(script); // <- TODO: Use `JavascriptExecutionTools.execute` here
eval(script); // <- TODO: Use `JavascriptExecutionTools.execute` here
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.
The component can run operating-system commands or spawn processes.
import { type ChildProcess } from 'child_process';import type { ChildProcess } from 'child_process';import { type ChildProcess } from 'child_process';import type { ChildProcess } from 'child_process';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.
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 →