@seoagent-official/seoagent@1.119.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 21d ago · by lpm-firewall-aiThe source shows first-party agent hook setup with automatic sync and a latest-package fallback, but installation requires the explicit init command. This is an agent extension lifecycle risk, not a confirmed attack.
Decision evidence
public snapshot- The package exposes a CLI entrypoint and declares no install lifecycle hook in its manifest.
- The explicit init command calls setup code that writes Claude project settings and registers session-start and file-edit hooks.
- Those hooks automatically run SEOAgent sync and may fall back to fetching the latest package with npx.
- The hook setup is reached through the user-invoked init command, not an npm install hook.
- The hook is project-scoped and invokes the package's own sync operation; no unrelated credential recipient or malicious action was identified.
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.119.0.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.119.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.