← Back to Scanner

gitlab-api Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

gitlab-api is an AI agent skill, created by d1gl3 and published at openclaw/skills. ClawSecure audited gitlab-api across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 55/100 (Medium Risk). The 4 findings concentrate in Command Injection, Policy Violation and Permissions Manifest, including Detects command injection patterns in agent skills: shell operators,... and Detects command injection patterns in agent skills: shell operators,.... 2 were rated high or critical severity.

Is gitlab-api safe?

ClawSecure audited gitlab-api and assigned a security score of 55/100 (Medium Risk), identifying 4 findings across Command Injection and Policy Violation. Review the findings below before installing.

What did ClawSecure find in gitlab-api?

ClawSecure identified 4 findings in gitlab-api, concentrated in Command Injection, Policy Violation and Permissions Manifest. 2 were rated high or critical severity. The most severe include Detects command injection patterns in agent skills: shell operators,... and Detects command injection patterns in agent skills: shell operators,....

How was gitlab-api audited?

ClawSecure ran gitlab-api through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 3 files from openclaw/skills.

What does a score of 55 mean?

ClawSecure assigned gitlab-api a security score of 55/100, placing it in the Medium Risk range. This reflects 4 findings led by Command Injection that warrant review before production use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for gitlab-api

ClawSecure detected 4 security findings in gitlab-api, spanning Command Injection, Policy Violation and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for gitlab-api

Harden command execution
gitlab-api constructs or runs system commands. Validate that commands are built only from trusted inputs, never pass user-controlled strings directly to a shell, and restrict execution to an allow-list of expected commands.
Resolve policy violations
gitlab-api trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent SecurityUnderstanding Our 3-Layer Audit ProtocolOWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security Standards

Related AI Agent Security Audits

@modelcontextprotocol/serversScore 50/100gitlab-cli-skillsScore 55/100xlsxScore 63/100docxScore 68/100skill-vetter-v2Score 70/100

Scanned on February 7, 2026. gitlab-api is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan