ClawAudit verdict

gitlab-api

45
🟠 Risky
Significant concerns — only install if you understand the risks

The skill interacts with the GitLab API using a personal access token stored in a file. While it follows best practices for token management, the use of `credential_access` capabilities raises concerns.

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

65
security
50
transparency
70
maintenance

Permission integrity

Makes network requests but does not declare curl/wget in required binaries

network_out

Findings (1)

Pattern match high

Possible hardcoded credential

scripts/gitlab_api.sh · prose · downgraded · TOKEN="${GITLAB_TOKEN:-$(cat ~/.config/gitlab/api_token 2>/dev/null)}

Permissions & capabilities

No declared permissions — minimal attack surface.

network_outcredential_accessdata_encoding

Is this flag fair?

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