@seoagent-official/seoagent@1.114.8
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 25d ago · by lpm-firewall-aiSource inspection found a CLI entrypoint without lifecycle hooks and package-owned skill setup invoked through project initialization. The scanner’s execution and network indicators did not establish an active attack in the inspected code.
Decision evidence
public snapshot- package.json exposes index.js as a CLI entrypoint; the inspected manifest has no lifecycle hooks.
- index.js names SEOAgent skill locations under .agents and .claude.
- The CLI writes the package-owned skill during project initialization, an explicit CLI command.
- The inspected child-process helper opens a URL using the platform browser command.
- No inspected source established credential theft, command-output exfiltration, or another active attack.
- The agent configuration behavior inspected installs the package’s own skill through a CLI command.
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 · L90A 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.8.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.114.8 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.