Is @ai-sdk/openai safe?

No malicious indicators - review capabilities before installing

Notable — review in context (capabilities are not malware):

Node.js shell/command execution

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

@ai-sdk/openai 4.0.42

npm_package · npm:@ai-sdk/openai

LOW

/ 100 risk score

Snapshot · scanned Aug 15, 2026 · @ai-sdk/openai@4.0.42 · 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 @ai-sdk/openai's authors. Report a false positive.

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

shell 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

Findings (1)

HIGHNode.js shell/command executionST-SHELL-NODE

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

src/openai-language-model-capabilities.ts:60-60

const match = /^o(\d+)(?:-|$)/.exec(modelId);

src/openai-language-model-capabilities.ts:71-71

const match = /^gpt-(\d+)(?:\.(\d+))?(?:-(.+))?$/.exec(modelId);

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 component

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