Caveat verdict

github

dev-workflow-automation

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

GitHub integration skill for listing repos, checking CI, and creating issues; credentials are read from env vars or config for the user's own GitHub account with explicit security guidance to protect the token.

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

45
security
90
transparency
80
maintenance

Findings (5)

Pattern match critical

Possible hardcoded credential

SKILL.md · code · TOKEN="ghp_your_token_here

Pattern match medium

Accesses OpenClaw config/secrets directly

SKILL.md · prose · downgraded · ~/.openclaw/openclaw.json

Pattern match medium

References child_process — can spawn system processes

test.js · prose · downgraded · child_process

Pattern match low

Accesses sensitive environment variables

api.js · prose · downgraded · process.env.GITHUB_TOKEN

Pattern match low

Popular HTTP library — network access

test.js · prose · downgraded · got

Permissions & capabilities

Requires 2 environment variables. (1 sensitive: GITHUB_TOKEN).

Is this flag fair?

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