@seoagent-official/seoagent@1.120.0
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 20d ago · by lpm-firewall-aiThe manifest exposes a CLI and has no npm lifecycle hook. The Claude integration and Bash-capable agent runner are part of explicit setup and processing commands, with no independent attack behavior established.
Decision evidence
public snapshot- The manifest exposes index.js as the seoagent CLI entrypoint.
- The agent integration targets local SEOAgent skill and Claude settings paths; setup runs through the init command and asks the user to confirm project creation.
- The installed Claude hooks run SEOAgent sync at session start and after tool use; they do not start the agent runner.
- Inbox processing is a separate CLI command that invokes the Claude Agent SDK; permission bypass is limited to its unattended mode.
- Setup can persist hooks in Claude settings, and the agent runner can use Bash; both are visible product capabilities.
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.120.0.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.120.0 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.