SkillTotal

Is paqad-ai safe?

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

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

paqad-ai 1.93.0

npm_package · npm:paqad-ai
LOW
0
/ 100 risk score
Snapshot · scanned Sep 27, 2026 · paqad-ai@1.93.0 · 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 paqad-ai's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
delegated authenticationinstall time executionnetwork 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
Delegated authentication
Tool Execution Context / User Delegated Credentials
Supply-chain provenance risk
General Protections / Supply Chain

Findings (4)

HIGHnpm install-time lifecycle hookST-INSTALL-NPM

package.json runs scripts automatically when the package is installed.

"postinstall": "node runtime/scripts/postinstall.mjs",

Why it matters: Install scripts are a favorite supply-chain foothold — they execute on every machine that installs the package.

Fix: Inspect the hook command. Install-time scripts are a common supply chain execution vector; ensure they do nothing beyond a documented build step.

HIGHNode.js shell/command executionST-SHELL-NODE

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

import { execFileSync } from "child_process";
import { execa } from "execa";
import { execFileSync } from "child_process";
import { execFileSync as execFileSync2 } from "child_process";
import { execFileSync as execFileSync3 } from "child_process";
import { execFileSync as execFileSync4 } from "child_process";
import { execa as execa2 } from "execa";
import { execa as execa3 } from "execa";
import { execa as execa4 } from "execa";
import { spawnSync } from "child_process";
const proc = spawnSync("node", [scriptPath], {
import { execFileSync as execFileSync5 } from "child_process";
import { execFileSync as execFileSync6 } from "child_process";
install: exec("pip install -r requirements.txt"),
test: exec("pytest"),
test_single: exec('pytest -k "<pattern>"'),
lint: exec("ruff check ."),
format: exec("ruff format ."),
migrate: exec(input2.migrate),
build: exec("python -m compileall .")
install: exec("bundle install"),
test: exec("bundle exec rspec"),
test_single: exec("bundle exec rspec <path_or_file>"),
lint: exec("bundle exec rubocop"),
format: exec("bundle exec rubocop -A"),

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("https://api.cohere.com/v1/rerank", {
const response = await fetch("https://api.osv.dev/v1/querybatch", {
const response = await fetch("https://api.cohere.com/v1/rerank", {

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.

LOWDelegated authentication (OAuth 2.0 / OIDC)ST-AUTH-DELEGATED

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. (11 occurrence(s) shown as evidence).

declare const SUPPORTED_CAPABILITIES: readonly ["inertia", "vue", "react", "tailwind", "boost", "pest", "phpunit", "docker", "compose", "sail", "next", "remix", "vite-spa", "gatsby", "nuxt", "quasar", "blazor", "ef-core", "minimal-api", "mv …
nextjs: ["app-router", "pages-router", "tailwind", "prisma", "trpc", "next-auth", "docker"],
"next-auth": "next-auth",
"@auth/core": "next-auth",
declare const CAPABILITIES: readonly ["inertia", "vue", "react", "tailwind", "boost", "pest", "phpunit", "docker", "compose", "sail", "next", "remix", "vite-spa", "gatsby", "nuxt", "quasar", "blazor", "ef-core", "minimal-api", "mvc", "razor …

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 component

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