@seoagent-official/seoagent@1.120.2
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 entrypoint and contains no lifecycle scripts. The agent hook is installed through an explicit setup command and performs the package’s documented sync operation, so the scanner’s execution and network indicators do not establish malicious behavior.
Decision evidence
public snapshot- package.json exposes index.js as the CLI entry and ends without lifecycle scripts.
- The indicated configuration location names .claude/settings.json and the SEOAgent skill directory.
- The project hook is installed through the explicit init command; it runs sync at session start and after write or edit tools.
- The sync command pushes and pulls project state with the dashboard and does nothing when the user is not logged in.
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.2.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.120.2 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.