@seoagent-official/seoagent@1.98.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 16d ago · by lpm-firewall-aiSource inspection found product-aligned CLI setup, project-local sync hooks, and limited opt-out telemetry. The scanner’s command-execution and network matches did not establish command-output exfiltration or another concrete attack.
Decision evidence
public snapshot- package.json exposes index.js as the seoagent CLI entrypoint; the inspected manifest has no lifecycle scripts.
- index.js identifies project-local Claude skill and settings paths, and its explicit init command sets up the project. Its sync hooks run at SessionStart and PostToolUse.
- Telemetry sends an install ID, event, CLI version, and platform; SEOAGENT_TELEMETRY and DO_NOT_TRACK can disable it.
- The Claude availability check suppresses command output and reads local session data; no command-output transfer 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 · L85A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L85Findings
Affected versions and remediation
This report applies to @seoagent-official/seoagent@1.98.0.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.98.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.