ClawAudit verdict

auditclaw-github

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

Uses GITHUB_TOKEN (read-only) via a clearly documented read-only API pattern; all data flows to a local SQLite database at ~/.openclaw/grc/compliance.sqlite with no external exfiltration beyond the expected GitHub API calls.

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

58
security
100
transparency
90
maintenance

Findings (3)

Pattern match critical

Possible hardcoded credential

README.md · code · TOKEN="your-token-here

Pattern match medium

subprocess execution — runs system commands from Python

scripts/github_evidence.py · prose · downgraded · subprocess.run(

Pattern match low

Python os.environ.get — reads environment variable

scripts/github_evidence.py · prose · downgraded · os.environ.get(

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

Requires 1 environment variable. (1 sensitive: GITHUB_TOKEN). Requires 1 system binary.

Is this flag fair?

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