Caveat verdict

vector-memory

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Local semantic memory search with optional vector sync; operates on local files only with no external network calls beyond described sync behavior.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

10
security
80
transparency
70
maintenance

Permission integrity

Accesses agent memory/configuration files

agent_memory

Findings (5)

Pattern match critical

Pipe-to-shell pattern (curl | sh) — supply chain attack vector

README.md · code · curl -sL https://raw.githubusercontent.com/YOUR_USERNAME/vector-memory-openclaw/

Pattern match critical

Pipe to bash — executes piped content as shell commands

README.md · code · | bash

Pattern match medium

References agent memory files

SKILL.md · code · MEMORY.md

Pattern match medium

References child_process — can spawn system processes

vector-memory/memory.js · prose · downgraded · child_process

Pattern match medium

Dynamic import() — loads module at runtime

vector-memory/vector_memory_local.js · prose · downgraded · import('

Why the tier is capped

Execution sink present in raw bytes (Hard Floor: class A/B/D). Final tier capped at Caution — cannot be lifted by any downgrade, example-payload opt-in, or allowlist.

Permissions & capabilities

No declared permissions — minimal attack surface.

agent_memory

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API