Versioned security assessment

Report ID: SA-EDC484C3

7/5/2026, 1:15:36 AM

secrets-gitleaks security assessment v7

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
secrets-gitleaks
Version
v7
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/devsecops/secrets-gitleaks
Coverage
12 Files scanned · 3,311 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 findings are expected Gitleaks documentation, configuration examples, or CI templates rather than live secret access. I confirmed one unsafe troubleshooting command and added a high-confidence semantic finding for unredacted Gitleaks reports that can expose detected secrets in CI logs or artifacts. No prompt injection attempt was found in the reviewed files.

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

12 Files scanned · 3,311 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 example pipes Gitleaks output into xargs and sh -c, embedding report-derived file and line values in a shell command. A crafted repository path could turn copied guidance into command injection.

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/gitlab-ci.yml:37-42assets/gitlab-ci.yml:62-65assets/gitlab-ci.yml:104-107
Unredacted Secret Reports in CI Templates
The GitHub and GitLab templates generate Gitleaks reports without redaction and upload or retain them as artifacts. The GitLab incremental job also prints new-findings.json to logs, which can expose detected secret values.
The report generation commands visibly omit redaction while artifacts and log output retain or print the generated reports. Gitleaks JSON findings can include secret material, so this is a credible exposure path.

Remediation

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

  1. FIX-001
    High
    Unredacted Gitleaks reports are generated and retained in CI templates.
    Add redaction to Gitleaks commands, avoid printing raw findings, restrict artifact access, and encrypt stored reports.
  2. FIX-002
    Medium
    A troubleshooting example uses xargs with sh -c on report-derived values.
    Replace it with a small script that validates numeric lines and quotes file paths safely before reading context.
  3. FIX-003
    Low
    Optional CI integrations use repository tokens and outbound notification services.
    Document least-privilege token scopes and require users to review Slack and GitLab notification steps before enabling them.

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