Is ctx7 safe?
- Node.js shell/command execution
- Node.js network egress
- Delegated authentication (OAuth 2.0 / OIDC)
ctx7 is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 3 risky constructs are reported for review. It can: delegated authentication, network egress and shell execution — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).
ctx7 0.5.12
Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of ctx7'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 (3)
The component can run operating-system commands or spawn processes.
import { execFileSync } from "child_process";import { spawn } from "child_process";const child = spawn(editor, [previewFile], {import { spawn as spawn2 } 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.
The component makes outbound network requests.
const response = await fetch(treeUrl, { headers });const response = await fetch(`${GITHUB_API}/repos/${owner}/${repo}`, { headers });const response = await fetch(rawUrl, { headers });const fileResponse = await fetch(rawUrl, { headers: ghHeaders });const response = await fetch(skillUrl, { headers: ghHeaders });const response = await fetch(`${baseUrl}/api/v2/skills?${params}`);const response = await fetch(`${baseUrl}/api/v2/skills?${params}`);const response = await fetch(`${baseUrl}/api/v2/skills?${params}`);const response = await fetch(`${baseUrl}/api/v2/skills/suggest`, {const response = await fetch(`${baseUrl}/api/v2/libs/search?${params}`, { headers });const response = await fetch(`${baseUrl}/api/v2/skills/quota`, {const response = await fetch(`${baseUrl}/api/v2/skills/questions`, {const response = await fetch(`${baseUrl}/api/v2/skills/generate`, {const response = await fetch(`${baseUrl}/api/v2/libs/search?${params}`, {const response = await fetch(`${baseUrl}/api/v2/context?${params}`, {fetch(`${getBaseUrl()}/api/v2/cli/events`, {return await fetch(url, {const response = await fetch(`${getBaseUrl()}/api/dashboard/whoami`, {const response = await fetch(`${getBaseUrl()}/api/dashboard/api-keys`, {const res = await fetch(`${base}/${filename}`);const response = await fetch(`${deployment.baseUrl}/api/auth/mcp`, {const response = await fetch(
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.
An OAuth 2.0 / OpenID Connect delegated-authentication flow was detected (authorization-code / refresh-token / token-exchange grant, an OIDC authorize/discovery endpoint or id_token, or a delegation library). Tools authenticate with the end user's delegated, scoped credentials rather than a long-lived embedded service credential.
grant_type: "refresh_token",
Fix: Delegated auth is a lower-blast-radius execution context than an embedded static credential. Confirm the requested scopes are minimal and that tokens are never logged or forwarded off-host.
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 →