@seoagent-official/seoagent@1.108.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 scanner’s execution and network indicators correspond to a CLI that checks Claude Code availability and performs package-aligned agent setup. The inspected source did not establish credential exfiltration, unconsented install-time mutation, or another concrete attack.
Decision evidence
public snapshot- The manifest identifies a CLI entrypoint and contains no lifecycle hook.
- The agent configuration paths are package-owned SEOAgent skill locations; the inspected initializer writes skill files there when explicitly run.
- Command execution checks for Claude Code and reads its credential state to decide whether the user can access the agent; no credential forwarding attack was established.
- No unconsented npm install hook or concrete malicious behavior was identified in the inspected source.
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 · L87A 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.108.0.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.108.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.