registry / @seoagent-official/seoagent / 1.122.0

@seoagent-official/seoagent@1.122.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-ai

The scanner’s process-execution and network findings are consistent with the CLI’s project and agent integration. Source inspection found no install-time execution or concrete attack behavior.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

The hooks are configured through the CLI refresh or sync flow; no npm install trigger was found.

Impact

The reviewed behavior supports product synchronization; no unauthorized disclosure or harmful action was established.

Mechanism

The CLI adds same-package sync hooks for session start and after writes in the project’s Claude settings.

AI rationale

The scanner’s process-execution and network findings are consistent with the CLI’s project and agent integration. Source inspection found no install-time execution or concrete attack behavior.

Decision evidence

public snapshot

AI called this Clean at 89.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The inspected manifest identifies a command-line product; it contains no npm lifecycle hook.
The CLI targets `.claude/settings.json` and adds sync hooks for session start and after writes while retaining existing settings.
Those hooks invoke this same package’s sync command.
Hook setup is reached through the CLI refresh flow, not npm installation.
The agent runner uses edit-accepting permissions by default; bypass mode is described as an explicit disposable-sandbox option requiring `--yes`.

Evidence against

Behavioral surface

Source

ChildProcessEnvironmentVarsNetworkShell

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 436 KB of source, external domains: 127.0.0.1, api.openai.com, api.replicate.com, console.anthropic.com, example.com, fal.run, registry.npmjs.org, seoagent.com, www.google.com

Source & flagged code

6 flagged

index.jsView file

9.sync-cursor L10: `,Wf=process.env.XDG_CONFIG_HOME&&process.env.XDG_CONFIG_HOME.trim().length>0?process.env.XDG_CONFIG_HOME:jt(Gf(),".config"),ee=jt(Wf,"seoagent"),tt=jt(ee,"auth.json"),Zo=jt(ee,"st... L11: `),i=eg(r),s=i.length>0?i[0].indent:0,[a]=Da(i,0,s);return{data:a,body:o}}function nt(e){if(!Xf(e))return null;try{return te(Qf(e,"utf-8"))}catch{return null}}function tg(e){if(e==... ... L15: `)?"":` L16: `)}import{existsSync as kr,readdirSync as ng,statSync as rg}from"fs";import{join as Je}from"path";var Ua=["svelte.config.js","svelte.config.ts","svelte.config.mjs","svelte.config.c... L17: `).map(t=>t.trim()).filter(Boolean):[]}function Sr(e,t,n={}){let r=n.execGit??ug,o=n.sourceExists??((m,w)=>ag(lg(m,w))),i=n.checkedCommit&&$r.test(n.checkedCommit)?n.checkedCommit:...

Critical

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution with blocking evidence.

index.jsView on unpkg · L9

96Trigger-reachable chain: manifest.main -> index.js L96: L97: `))}function P(e,t,n,r=n){e?e.stop(r):d[t](n)}var $c=[{suffixes:[".wordpress.com"],platform:{id:"wordpress.com",label:"WordPress.com",api:"wordpress",enableHint:"an application pas... L98: `,"utf-8"),n}catch{return null}}import{execFileSync as Yh}from"child_process";var zh=2048,Jh=200,Xh=10,Qh=/^[A-Za-z0-9._-]+$/,Zh=/^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\.[a-z0-9]([a-z0-9-... L99: `).replace(/\n+$/,`

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

Findings

2 Critical5 High3 Medium2 Low

CriticalSame File Env Network Executionindex.js

CriticalTrigger Reachable Dangerous Capabilityindex.js

HighChild Processindex.js

HighShell

HighCommand Output Exfiltrationindex.js

HighTrigger Reachable Command Output Exfiltrationindex.js

HighSemantic Analysis Limitedindex.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @seoagent-official/seoagent@1.122.0.

See all versions of @seoagent-official/seoagent for other recorded verdicts.

Review the evidence and your use of @seoagent-official/seoagent@1.122.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: 2026-10-16 16:51:20.996Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

registry / @seoagent-official/seoagent / 1.122.0

@seoagent-official/seoagent@1.122.0

AI Security Review

scanned 19d ago · by lpm-firewall-ai

The scanner’s process-execution and network findings are consistent with the CLI’s project and agent integration. Source inspection found no install-time execution or concrete attack behavior.

Static reason

High-risk behavior combination matched malicious policy.

Trigger

The hooks are configured through the CLI refresh or sync flow; no npm install trigger was found.

Impact

The reviewed behavior supports product synchronization; no unauthorized disclosure or harmful action was established.

Mechanism

The CLI adds same-package sync hooks for session start and after writes in the project’s Claude settings.

AI rationale

The scanner’s process-execution and network findings are consistent with the CLI’s project and agent integration. Source inspection found no install-time execution or concrete attack behavior.

Decision evidence

public snapshot

AI called this Clean at 89.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

The inspected manifest identifies a command-line product; it contains no npm lifecycle hook.
The CLI targets `.claude/settings.json` and adds sync hooks for session start and after writes while retaining existing settings.
Those hooks invoke this same package’s sync command.
Hook setup is reached through the CLI refresh flow, not npm installation.
The agent runner uses edit-accepting permissions by default; bypass mode is described as an explicit disposable-sandbox option requiring `--yes`.

Evidence against

Behavioral surface

Source

ChildProcessEnvironmentVarsNetworkShell

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 1 file(s), 436 KB of source, external domains: 127.0.0.1, api.openai.com, api.replicate.com, console.anthropic.com, example.com, fal.run, registry.npmjs.org, seoagent.com, www.google.com

Source & flagged code

6 flagged

index.jsView file

Critical

Same File Env Network Execution

A single source file combines environment access, network access, and code or shell execution with blocking evidence.

index.jsView on unpkg · L9

Critical

Trigger Reachable Dangerous Capability

A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.

Findings

2 Critical5 High3 Medium2 Low

CriticalSame File Env Network Executionindex.js

CriticalTrigger Reachable Dangerous Capabilityindex.js

HighChild Processindex.js

HighShell

HighCommand Output Exfiltrationindex.js

HighTrigger Reachable Command Output Exfiltrationindex.js

HighSemantic Analysis Limitedindex.js

MediumNetwork

MediumEnvironment Vars

MediumStructural Risk Force Deep Review

LowHigh Entropy Strings

LowUrl Strings

Affected versions and remediation

This report applies to @seoagent-official/seoagent@1.122.0.

See all versions of @seoagent-official/seoagent for other recorded verdicts.

Review the evidence and your use of @seoagent-official/seoagent@1.122.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: 2026-10-16 16:51:20.996Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.