Versioned security assessment

Report ID: SA-61E7FD0A

6/29/2026, 3:40:06 AM

git-workflow-enforcer security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
git-workflow-enforcer
Version
v6
Maintainer
CrazyDubya
Coverage
1 Files scanned · 216 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

2 confirmed security findings require 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 command-execution and weak-crypto matches, but most are markdown examples for Git workflow guidance or false positives from git terminology. Confirmed concerns are legitimate but elevated: the skill allows Bash and Write, suggests npm/npx execution, creates hook/template files, and shows a global Git configuration change under the home directory.

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

1 Files scanned · 216 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.

Not recorded by this audit

Filesystem access

May read or write local files.

Observed in 3 evidence locations

Env variables

May read values from the process environment.

Observed in 1 evidence location

External commands

May invoke commands or programs outside the Skill.

Observed in 5 evidence locations

Risk findings

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

Confirmed security concerns (2)

RISK-001 Medium
Repository Command Execution Guidance
The skill requests Bash access and provides shell examples for npm scripts, git log filtering, npx standard-version, and Git configuration. This is expected for a Git workflow skill, but running npm or npx in an untrusted repository can execute project-controlled or downloaded code, so command execution should remain user-reviewed.
The command examples are real shell commands and the skill declares Bash access. The intent appears legitimate, but npm and npx execution are meaningful risks in untrusted repositories.
RISK-002 Medium
Global Git Configuration and Home Directory Template
The skill shows creating a .gitmessage file and setting it as the global commit template. This is not malicious, but it changes user-level Git behavior outside the current repository and writes to a hidden file in the home directory.
The home-directory path and global Git configuration command are directly present. The behavior is documented and workflow-related, which lowers concern from high to medium.

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 (2)
Low
Static Pattern False Positives in Markdown Examples
Many reported Ruby backtick, shell substitution, and weak cryptographic algorithm matches come from markdown code fences, inline Git examples, conventional commit text, or git hash terminology. No evidence found of Ruby backtick execution, cryptographic implementation, malware, network exfiltration, or prompt injection in the skill file.
The cited lines are documentation, templates, or Git examples rather than executable Ruby or weak cryptographic code. Manual review found no hidden override instructions or exfiltration logic.
Low
Secret Keyword Scan Is Defensive
The api_key, password, and secret terms appear in a pre-commit hook example that blocks staged sensitive data. This is a defensive scan pattern rather than an attempt to read or transmit credentials.
The command searches staged diffs and exits with an error when secret-like text is found. There is no network sink or storage destination for matched data.

Verify and export

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

Audit attestation: not_attestable