@seoagent-official/seoagent@1.101.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 28d ago · by lpm-firewall-aiThe inspected source aligns with the package’s stated SEO CLI purpose, and the agent integration is exposed through explicit CLI setup. The scanner’s execution and network hints do not establish an attack in the reviewed source.
Decision evidence
public snapshot- The manifest describes a CLI for SEO work with Claude Code, consistent with the package’s stated purpose.
- The entrypoint identifies project skill and Claude settings paths as SEOAgent integration locations.
- The uninstall path requires a confirmation prompt before removing a detected hook integration.
- Agent SDK use and credential checks appear in the CLI entrypoint as part of its Claude Code workflow.
- Project initialization is exposed as an explicit `seoagent init` 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 · L85A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
index.jsView on unpkg · L85Findings
Affected versions and remediation
This report applies to @seoagent-official/seoagent@1.101.0.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.101.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.