Caveat verdict

openclaw-key-management

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

Local credential vault using AES-256-GCM encryption for protecting API keys stored in OpenClaw memory files; all operations are local with explicit security design to keep credentials off memory files.

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

60
security
80
transparency
90
maintenance

Permission integrity

Accesses agent memory/configuration files

agent_memory

Findings (2)

Pattern match critical

Possible hardcoded credential

USAGE.md · code · SECRET:" MEMORY.md

Pattern match medium

References agent memory files

SKILL.md · code · MEMORY.md

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

No declared permissions — minimal attack surface.

credential_accessagent_memory

Is this flag fair?

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