@seoagent-official/seoagent@1.100.3
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 16d ago · by lpm-firewall-aiThe scanner’s command and network matches resolve to local Claude CLI and Keychain checks, ordinary CLI networking, and limited package-service telemetry. The manifest has no lifecycle hooks, and the inspected source does not establish an attack.
Decision evidence
public snapshot- package.json exposes index.js as a CLI entrypoint and declares no lifecycle scripts.
- index.js defines local skill and settings paths; the CLI command parser runs when invoked.
- Claude credential checks only classify local session availability; Keychain output is parsed locally.
- Telemetry sends an install ID, event, CLI version, and platform to the package service; an opt-out is supported.
- No inspected source shows command output or credentials being sent to an unrelated recipient.
- The reported shell calls check for the Claude CLI or inspect the local macOS Keychain; their output is not transmitted.
Source & flagged code
7 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.100.3.
See all versions of @seoagent-official/seoagent for other recorded verdicts.
- Review the evidence and your use of @seoagent-official/seoagent@1.100.3 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.