ClawAudit verdict
supabase-vault
A Supabase Vault secret storage backend for OpenClaw that replaces local secrets.json with AES-256 encrypted Postgres storage; it is transparent about its architecture and bootstrap credentials are protected by OS keychain.
⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.
Automated static analysis — not a human review. ClawAudit flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.
Permission integrity
package_install
Findings (6)
Possible hardcoded credential
references/architecture.md · code · API_KEY = "sk-proj-...
Accesses system credential store
SKILL.md · frontmatter · keychain
Accesses OpenClaw config/secrets directly
SKILL.md · prose · downgraded · ~/.openclaw/openclaw.json
References child_process — can spawn system processes
assets/rpc-handler.ts · prose · downgraded · child_process
Reads files from sensitive system paths
scripts/crypto-local.js · prose · downgraded · readFileSync("/etc
Uses spawn() — can execute external programs
scripts/keychain.js · prose · downgraded · spawn(
Why the tier is capped
Execution sink present in raw bytes (Hard Floor: class 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.
package_installnetwork_incredential_store Is this flag fair?
Thanks — recorded.