Versioned security assessment

Report ID: SA-AF41D7FF

6/28/2026, 6:25:19 AM

secrets-gitleaks security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
secrets-gitleaks
Version
v6
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

Low

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.

Static analysis reported many high-risk patterns, but review found they are mostly defensive Gitleaks rules, CI templates, and remediation examples rather than malicious code. No prompt injection or data exfiltration intent was found. Publication is acceptable with a warning because the CI examples execute external commands, read scan reports, upload artifacts, and include some fail-open examples.

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

4 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 4 evidence locations

Filesystem access

May read or write local files.

Observed in 4 evidence locations

Env variables

May read values from the process environment.

Observed in 4 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 4 evidence locations

Capability review items (3)
Medium
assets/github-action.yml:55-61assets/github-action.yml:97-100assets/gitlab-ci.yml:153-179assets/gitlab-ci.yml:187-189
Executable CI Templates Process Repository Contents
Verdict: TRUE_POSITIVE for external command and filesystem access, but legitimate for a Gitleaks skill. The GitHub and GitLab templates run Gitleaks in CI, read generated reports, and upload artifacts. This can expose sensitive findings if artifact access is too broad. Confidence: 0.82. Confidence reasoning: the commands and file reads are explicit, but their purpose is defensive scanning rather than covert exfiltration.
Medium
assets/github-action.yml:55-61assets/github-action.yml:75-81assets/github-action.yml:167-173assets/gitlab-ci.yml:38-42assets/gitlab-ci.yml:46-50assets/gitlab-ci.yml:130-134
Fail-Open Secret Scanning Examples
Verdict: TRUE_POSITIVE as a workflow risk. Several examples suppress scanner exit codes with exit-code zero or shell true. Some sections add later checks, but users who copy only the command may create secret gates that pass after findings. Confidence: 0.76. Confidence reasoning: the fail-open commands are visible, while final impact depends on how users copy and deploy the templates.
Low
SKILL.md:19-21assets/precommit-config.yaml:6-10assets/github-action.yml:112assets/gitlab-ci.yml:218-222
Hardcoded URL Findings Are Expected References
Verdict: FALSE_POSITIVE for malicious network behavior. The URLs point to official Gitleaks, OWASP, CWE, pre-commit, GitHub, or CI API resources used by documentation and templates. Confidence: 0.88. Confidence reasoning: the URLs are visible references or platform endpoints, with no hidden outbound data channel found.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Low
SKILL.md:156-160assets/config-custom.toml:57-65references/detection_rules.md:198-236
Credential Pattern Findings Are Documentation Examples
Verdict: FALSE_POSITIVE for embedded secret theft. The API key, private key, token, and password strings are detection rules or placeholder patterns. They describe what Gitleaks should find and do not contain real credentials. Confidence: 0.91. Confidence reasoning: the surrounding headings and fields identify these as rule definitions and examples, not operational secrets.

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.

Static false positives ignored (1)
Low
references/compliance_mapping.md:71-83references/remediation_guide.md:506-526SKILL.md:1-8
Malware Keyword Findings Are Contextual False Positives
Verdict: FALSE_POSITIVE. Static malware and C2 keyword hits appear in compliance and remediation reference material about security controls, not in instructions to deploy malware. No prompt injection language was found. Confidence: 0.84. Confidence reasoning: the reviewed files consistently discuss defensive secret detection and incident response, though broad markdown keyword matches require human context.

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