Versioned security assessment

Report ID: SA-777E2DC5

7/6/2026, 1:08:06 AM

reviewdog security assessment v7

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
reviewdog
Version
v7
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/secsdlc/reviewdog
Coverage
7 Files scanned · 2,087 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Critical

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.

I found no evidence of prompt injection or malicious data exfiltration in the skill text. Most static alerts are safe documentation examples or expected reviewdog CI configuration. Confirmed risks are the GitLab CI remote installer pipe-to-shell pattern and a predictable temporary Gitleaks report path.

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

7 Files scanned · 2,087 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.

Observed in 2 evidence locations

Network access

May connect to external services.

Observed in 19 evidence locations

Filesystem access

May read or write local files.

Observed in 20 evidence locations

Env variables

May read values from the process environment.

Observed in 17 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 49 evidence locations

Capability review items (3)
Medium
assets/pre_commit_config.yaml:42
Standard device file access
entry: bash -c 'gitleaks detect --report-format json --report-path /tmp/gitleaks.json --no-git 2>/de
The hook writes Gitleaks output to a predictable /tmp/gitleaks.json path. Secret scan reports can contain sensitive values, so this can leak data or collide with another local process.
Medium
assets/pre_commit_config.yaml:42
Temp directory access
entry: bash -c 'gitleaks detect --report-format json --report-path /tmp/gitleaks.json --no-git 2>/de
The hook stores a Gitleaks report in a fixed temporary path under /tmp. Because these reports may include secrets, the file should use a private temporary file and be deleted after use.
Low
assets/gitlab_ci_template.yml:14
Hardcoded URL
curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b /usr
The hardcoded URL is used to fetch a remote installer during CI. The risk is supply-chain exposure from an external mutable dependency, especially because the script is executed immediately.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Critical
assets/gitlab_ci_template.yml:14
Pipe to shell pattern
curl -sfL https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b /usr
The GitLab CI template downloads an installer from a mutable raw GitHub branch and executes it with sh. This creates a real supply-chain execution risk without pinning or checksum verification.

Remediation

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

  1. FIX-001
    Critical
    Remote installer is piped directly to the shell in assets/gitlab_ci_template.yml.
    Download a pinned release artifact, verify checksum or signature, then execute from a controlled path. Avoid mutable branch installers.
  2. FIX-002
    Medium
    Gitleaks results are written to a predictable /tmp path in assets/pre_commit_config.yaml.
    Use mktemp with restrictive permissions, store reports inside a protected workspace, and delete the file after reviewdog consumes it.
  3. FIX-003
    Low
    CI examples rely on platform tokens and several unpinned tool versions.
    Document least privilege token scopes and pin reviewdog, scanner, and container versions for reproducible builds.

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