ClawAudit verdict

glm-plan-usage

openclaw-glm-plan-usage

88
🟢 Trusted
Low risk — reviewed by ClawAudit, behavior matches stated purpose

Queries GLM coding plan usage statistics by reading local OpenClaw config to detect the GLM provider and calling that provider usage API; reads credential from config for its own provider API, consistent with stated purpose.

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

0
security
60
transparency
90
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Installs packages at runtime — transitive dependencies are not auditable

package_install

Findings (6)

Pattern match critical

Recursive delete from root or home — destructive command

docs/INSTALLATION.md · code · rm -rf ~

Pattern match critical

Possible hardcoded credential

references/api-endpoints.md · code · API_KEY="your-api-key-here

Pattern match high

References sudo — requests elevated privileges

SKILL.md · code · sudo

Pattern match high

apt-get install — installs system packages

SKILL.md · code · apt-get install

Pattern match high

Accesses OpenClaw config/secrets directly

SKILL.md · code · ~/.openclaw/openclaw.json

Pattern match high

yum install — installs system packages

docs/INSTALLATION.md · code · yum install

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.

package_installcredential_access

Is this flag fair?

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