Versioned security assessment

Report ID: SA-D46E6208

7/7/2026, 10:11:09 PM

secrets-gitleaks security assessment v8

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
secrets-gitleaks
Version
v8
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/devsecops/secrets-gitleaks
Coverage
13 Files scanned · 3,321 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

1 confirmed security finding requires attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Most static hits are expected Gitleaks documentation, regex examples, placeholder credentials, public URLs, and CI snippets. I confirmed one static issue where an xargs sh -c troubleshooting command can execute shell text using report-derived values. I also found a semantic risk where CI templates store unredacted secret scan reports as artifacts.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

13 Files scanned · 3,321 Lines analyzed

2 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 26 evidence locations

Filesystem access

May read or write local files.

Observed in 8 evidence locations

Env variables

May read values from the process environment.

Observed in 33 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 92 evidence locations

Capability review items (1)
Medium
references/false_positives.md:562
xargs command (can execute arbitrary commands)
gitleaks detect --report-format json | jq -r '.[0] | .File, .StartLine' | xargs -I {} sh -c 'sed -n
The troubleshooting command pipes report-derived file and line values into xargs with sh -c. A crafted filename could alter the copied shell command, although the example is not auto-executed by the skill.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (1)

RISK-001 High
assets/github-action.yml:52-70assets/github-action.yml:165-180assets/gitlab-ci.yml:37-70assets/gitlab-ci.yml:94-115assets/gitlab-ci.yml:127-139assets/gitlab-ci.yml:187-189
Unredacted Secret Reports Stored as CI Artifacts
The CI templates generate Gitleaks JSON or SARIF reports without an explicit redaction flag and upload them as artifacts. Gitleaks reports can include sensitive secret values or metadata, so artifact storage can widen exposure.
The templates explicitly create report files and upload or retain them as artifacts, but the commands shown do not include --redact. The skill documentation itself warns that reports can contain sensitive findings.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    CI templates store raw Gitleaks reports as artifacts.
    Add --redact to report-generating commands, restrict artifact access, shorten retention, and share summaries instead of raw reports.
  2. FIX-002
    Medium
    Troubleshooting guidance uses xargs with sh -c on report-derived values.
    Replace it with a small script that validates file paths and line numbers without invoking a shell.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable