Skills gitlab Audit History
📦

Audit History

gitlab - 8 audits

Version comparison

Capability and finding changes across audited versions, newest first.

VersionDateResultReview itemsChange vs previous
v8 LatestJul 5, 2026, 03:03 PM 1 confirmed0No capability change
v7 Jul 5, 2026, 03:03 PM 1 confirmed0 Network accessFilesystem access
v6 Jun 30, 2026, 12:54 AM No confirmed findings2Network accessFilesystem access
v5 Jan 17, 2026, 05:22 AM No confirmed findings0No capability change
v4 Jan 17, 2026, 05:22 AM No confirmed findings0External commands
v3 Jan 10, 2026, 02:36 PM No confirmed findings0No capability change
v2 Jan 10, 2026, 02:36 PM No confirmed findings0No capability change
v1 Jan 10, 2026, 02:36 PM No confirmed findings0Baseline

Jul 5, 2026, 03:03 PM

The static backtick detections are false positives because SKILL.md contains Markdown command references, not executable Ruby or shell code. A high-confidence semantic risk remains: several GitLab write operations are documented without an explicit confirmation requirement. No evidence found for prompt injection attempts.

1
Files scanned
72
Lines analyzed
2
Review items
0
False positives ignored

Confirmed security concerns (1)

High
State-Changing GitLab Operations Lack Explicit Confirmation
SKILL.md lists commands that can merge or approve merge requests, close issues, and run or retry pipelines. The guidance only requires authentication and does not require explicit confirmation before these write operations.
The cited command reference includes merge, approve, close, CI run, and retry actions, while the pre-operation guidance only checks authentication. These actions can alter repository state or trigger CI costs.
Audited by: codex

Jul 5, 2026, 03:03 PM

The static backtick detections are false positives because SKILL.md contains Markdown command references, not executable Ruby or shell code. A high-confidence semantic risk remains: several GitLab write operations are documented without an explicit confirmation requirement. No evidence found for prompt injection attempts.

1
Files scanned
72
Lines analyzed
2
Review items
0
False positives ignored

Confirmed security concerns (1)

High
State-Changing GitLab Operations Lack Explicit Confirmation
SKILL.md lists commands that can merge or approve merge requests, close issues, and run or retry pipelines. The guidance only requires authentication and does not require explicit confirmation before these write operations.
The cited command reference includes merge, approve, close, CI run, and retry actions, while the pre-operation guidance only checks authentication. These actions can alter repository state or trigger CI costs.
Audited by: codex

Jun 30, 2026, 12:54 AM

The static Ruby backtick and weak cryptography findings are false positives caused by Markdown command examples and words like description or Desc. The skill is not malicious, but it intentionally guides external glab commands that can modify GitLab resources, trigger CI, and clone repositories, so publication should include an operational risk warning.

1
Files scanned
72
Lines analyzed
5
Review items
2
False positives ignored
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium
Mutating GitLab CLI Operations
The skill documents glab commands that can create, merge, approve, close, or comment on GitLab resources. These commands are legitimate for a GitLab helper, but they require explicit user confirmation before execution.
The referenced lines directly list glab commands that change merge requests and issues. The behavior is intentional and not malicious, but it can affect remote project state.
Medium
CI Pipeline Execution Commands
The skill includes commands to run and retry GitLab CI pipelines. Triggering CI can consume runner resources or deploy code depending on the repository configuration.
The command reference and behavioral guideline explicitly mention status checks, running CI, and retrying failed CI. The risk depends on repository permissions and pipeline configuration.
Static false positives ignored (2)

These static matches were dismissed by semantic review or matched schema-only tokens, so they are shown for transparency but do not drive the quality score.

Low
Static Backtick Execution False Positive
The analyzer reported Ruby or shell backtick execution, but the evidence is Markdown inline code and fenced bash examples. No executable Ruby code or dynamic shell wrapper is present in the skill file.
The only file is Markdown documentation, and the backticks delimit command examples rather than executable code. No evidence found of Ruby execution syntax in an executable file.
Low
Weak Cryptography False Positive
The weak cryptography detections appear to match ordinary description text and placeholder words such as Desc. No cryptographic algorithm use is present in the skill file.
The referenced lines contain metadata and glab command examples, not calls to cryptographic libraries or algorithms. No evidence found of encryption, hashing, or signature logic.

Detected Patterns

External glab Command Guidance
Audited by: codex

Jan 17, 2026, 05:22 AM

Pure documentation skill containing only prompt guidelines and glab command references. Static findings are false positives: SHA-256 hashes flagged as weak crypto (SHA-256 is secure), 'sudo' in package installation docs flagged as privilege escalation (legitimate apt install command), content hashes flagged as C2 keywords (standard Git metadata), backtick notation flagged as shell execution (standard markdown documentation), and git remote detection flagged as reconnaissance (legitimate GitLab detection). No executable code or security risks present.

2
Files scanned
248
Lines analyzed
1
Review items
0
False positives ignored
Audited by: claude

Jan 17, 2026, 05:22 AM

Pure documentation skill containing only prompt guidelines and glab command references. Static findings are false positives: SHA-256 hashes flagged as weak crypto (SHA-256 is secure), 'sudo' in package installation docs flagged as privilege escalation (legitimate apt install command), content hashes flagged as C2 keywords (standard Git metadata), backtick notation flagged as shell execution (standard markdown documentation), and git remote detection flagged as reconnaissance (legitimate GitLab detection). No executable code or security risks present.

2
Files scanned
248
Lines analyzed
1
Review items
0
False positives ignored
Audited by: claude

Jan 10, 2026, 02:36 PM

Pure prompt-based documentation skill with no executable code. Provides guidance on using glab CLI for GitLab operations. No filesystem access, network calls, or code execution capabilities beyond documented command references.

1
Files scanned
72
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude

Jan 10, 2026, 02:36 PM

Pure prompt-based documentation skill with no executable code. Provides guidance on using glab CLI for GitLab operations. No filesystem access, network calls, or code execution capabilities beyond documented command references.

1
Files scanned
72
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude

Jan 10, 2026, 02:36 PM

Pure prompt-based documentation skill with no executable code. Provides guidance on using glab CLI for GitLab operations. No filesystem access, network calls, or code execution capabilities beyond documented command references.

1
Files scanned
72
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were recorded for this completed audit.
Audited by: claude