@seoagent-official/seoagent@1.106.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 28d ago · by lpm-firewall-aiStatic source inspection found a concrete conditional credential-forwarding risk: an operator-configured API base receives stored SEOAgent tokens during sync. The behavior is gated by user configuration and login, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- package.json exposes a CLI entrypoint and shows no npm lifecycle hook.
- The flagged entrypoint location identifies the Claude skill and settings paths.
- SEOAGENT_API_BASE can replace the default seoagent.com API base.
- The CLI stores login tokens and the selected API base; sync uses those tokens with that base.
- Claude hooks run sync at session start and after Write or Edit operations.
- The sync request sends its Authorization header to the selected API base.
- The credential flow is conditional on login and sync; no hidden token collection or unrelated fixed recipient was identified.
- The agent hooks are installed through the CLI setup flow, not an npm install hook.
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 · L87A 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.106.1.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.106.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.