@seoagent-official/seoagent@1.114.7
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 27d ago · by lpm-firewall-aiThe manifest exposes a CLI without install lifecycle hooks, and the inspected hook setup supports the package’s project sync workflow. Scanner flags for command execution and credential handling did not establish an unrelated data recipient or a concrete attack.
Decision evidence
public snapshot- package.json exposes index.js as a CLI and declares no lifecycle hooks.
- index.js defines a Claude settings hook that runs SEOAgent sync and writes that hook into project settings through CLI setup logic.
- The hook targets .claude/settings.json and invokes this package’s sync command; its behavior is tied to SEOAgent’s own project workflow.
- The Claude credential checks shown inspect credential availability and validity; no unrelated credential recipient or exfiltration was established.
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 · L89A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsFindings
Affected versions and remediation
This report applies to @seoagent-official/seoagent@1.114.7.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.114.7 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.