@seoagent-official/seoagent@1.123.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 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and source inspection found no concrete credential theft or unrelated exfiltration. The flagged shell, network, and agent capabilities support the package's user-invoked CLI and setup workflows.
Decision evidence
public snapshot- The manifest exposes the CLI through index.js and contains no npm lifecycle script.
- The project-local .claude/settings.json target receives session-start and post-write/edit sync hooks during explicit project setup.
- Those hooks run the package's sync command.
- Unattended processing requires --yes, is documented for disposable sandboxes, and withholds sensitive action types that lack owner approval.
- Initialization telemetry goes to the SEOAgent API and can be disabled through telemetry or do-not-track environment settings.
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.123.0.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.123.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.