Is ai 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

ai 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).

ai 7.0.66

npm_package · npm:ai

LOW

/ 100 risk score

Snapshot · scanned Aug 15, 2026 · ai@7.0.66 · 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'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.

src/generate-text/smooth-stream.ts:98-98

const match = chunkingRegex.exec(buffer);

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.

src/agent/pipe-agent-ui-stream-to-response.ts:7-7

import type { ServerResponse } from 'node:http';

src/generate-text/stream-text-result.ts:3-3

import type { ServerResponse } from 'node:http';

src/generate-text/stream-text.ts:24-24

import type { ServerResponse } from 'node:http';

src/realtime/realtime-session.ts:110-110

const response = await fetch(this.api.token, {

src/text-stream/pipe-text-stream-to-response.ts:1-1

import type { ServerResponse } from 'node:http';

src/ui-message-stream/pipe-ui-message-stream-to-response.ts:1-1

import type { ServerResponse } from 'node:http';

src/ui/call-completion-api.ts:57-57

const response = await fetch(api, {

src/ui/http-chat-transport.ts:191-191

const response = await fetch(api, {

src/ui/http-chat-transport.ts:246-246

const response = await fetch(api, {

src/util/write-to-server-response.ts:1-1

import type { ServerResponse } from 'node:http';

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 →