@seoagent-official/seoagent@1.130.1
The persistent AI SEO agent for Claude Code. Audits, keyword strategy, briefs, articles, real product screenshots from your repo, and the autopilot loop (cloud detects → CLI executes → ack closes) — other SEO tools write the prompt, SEOAgent runs it.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source behavior matches the package’s stated purpose as an SEO agent CLI. Although it has powerful agent and shell capabilities, the inspected credential, network, and telemetry flows did not show an attack.
Decision evidence
public snapshot- The manifest identifies this as an SEO agent CLI and exposes index.js as its command entry point; it defines no lifecycle scripts.
- Anthropic credential checks occur in the agent integration, which invokes the Claude Agent SDK for task execution.
- The unattended agent path is called with a task prompt and has explicit budget and turn limits.
- Telemetry code documents the event data and an opt-out; the inspected sender submits an install ID, event, CLI version, and platform.
- The entry point uses child-process execution and grants the agent Bash access, including a bypass-permissions mode for unattended tasks; these capabilities are part of its described agent function.
- The package has runtime network access to SEOAgent and image-provider APIs for its CLI features.
Source & flagged code
6 flaggedA single source file combines environment access, network access, and code or shell execution with blocking evidence.
index.jsView on unpkg · L9A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
Findings
Affected versions and remediation
This report applies to @seoagent-official/seoagent@1.130.1.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.130.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.