Caveat verdict

shared-memory

ling-mem

45
🟠 Risky
Significant risk patterns flagged — automated deep scan, not behavioral proof.

The skill silently installs a remote binary via `bash <(curl -fsSL https://raw.githubusercontent.com/...)` if the ling-mem CLI is not already present, and explicitly instructs to do this without asking the user; while SHA-256 verification is mentioned, executing remotely-fetched code automatically is a genuine RISKY pattern.

⚠ 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.

50
security
60
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Findings (4)

Pattern match high

HTTP request to bare IP address — common in malicious payloads

references/dream-flow.md · code · http://127.0.0.1

Pattern match medium

Instructs covert action — may act without user awareness

SKILL.md · prose · downgraded · silently

Pattern match low

References agent configuration files

doc/shared-memory-design.md · prose · downgraded · CLAUDE.md

Pattern match low

Popular HTTP library — network access

scripts/scan.sh · prose · downgraded · got

Why the tier is capped

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

Permissions & capabilities

Requires 1 system binary.

network_out

Is this flag fair?

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