@seoagent-official/seoagent@1.89.3
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 16d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the flagged entrypoint behavior is consistent with a user-invoked SEO CLI. Scanner indicators for command execution and network activity do not establish command-output exfiltration or another concrete attack in the inspected source.
Decision evidence
public snapshot- package.json defines a CLI entrypoint and dependencies; inspection of the full manifest found no lifecycle scripts.
- index.js identifies .claude/settings.json as a sync-hook location, and the package exposes setup through an explicit init command.
- Telemetry is sent during CLI initialization to the SEOAgent API; the source provides telemetry opt-out controls.
- The flagged child_process usage checks whether Claude Code is installed and reads its credential status; no command-output exfiltration was established.
Source & flagged code
7 flaggedA single source file combines environment access, network access, and code or shell execution with blocking evidence.
index.jsView on unpkg · L79A 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.89.3.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.89.3 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.