@seoagent-official/seoagent@1.120.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 19d ago · by lpm-firewall-aiThe manifest points to a CLI entrypoint and contains no install lifecycle hooks. The scanner’s combined network, environment, and subprocess indicators did not establish malicious behavior in the inspected source.
Decision evidence
public snapshot- The manifest exposes index.js as a CLI and defines no lifecycle scripts.
- The agent configuration path is a project-local Claude settings file; the CLI uses it to detect its own sync hook.
- The telemetry send shown is tied to an explicit reinitialization action and can be disabled through telemetry settings.
- The git subprocess uses fixed git arguments with a project path and a short timeout; no command-output exfiltration was established.
- The bundle includes network requests, environment checks, and subprocess calls, but inspected source did not establish a concrete attack chain.
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.3.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.120.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.