Versioned security assessment

Report ID: SA-7EF8DC07

7/1/2026, 12:45:16 AM

github-actions-templates security assessment v5

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
github-actions-templates
Version
v5
Maintainer
wshobson
Coverage
1 Files scanned · 334 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.

The static analyzer flagged many command, credential, network, filesystem, and weak-crypto patterns. Most are false positives caused by Markdown GitHub Actions examples, but the templates include mutable third-party action references and long-lived AWS credential examples that need publication warnings.

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 · 334 Lines analyzed

7 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 1 evidence location

Filesystem access

May read or write local files.

Observed in 1 evidence location

Env variables

May read values from the process environment.

Observed in 3 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 25 evidence locations

Capability review items (5)
Medium
Long-Lived Cloud Credential Template
The Kubernetes deployment example configures AWS access key and secret access key values from GitHub secrets. This is a legitimate pattern, but it encourages long-lived cloud credentials instead of short-lived OIDC federation.
The workflow clearly uses AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY from secrets. This is not exfiltration, but it creates avoidable credential exposure if copied directly.
Low
Credential References Use GitHub Secrets Context
The token and secret references use GitHub Actions secrets syntax. This is normal for workflow templates and does not show hardcoded credentials or credential exfiltration.
The values are placeholders under the GitHub secrets context. No literal secret value or external transfer of those secrets was found in the reviewed file.
Low
Hardcoded URL Is Placeholder Metadata
The hardcoded URL is an example production environment URL in a deployment template. It does not receive data or trigger a network request by itself.
The URL is https://app.example.com inside an environment metadata field. It is not used as an endpoint for sending credentials or repository data.
Low
Hidden Path Is Standard Workflow Location
The hidden file access finding points to .github/workflows in a reusable workflow example. This is the standard GitHub Actions workflow directory.
The path is used in a workflow_call example for a local reusable workflow. It is expected for GitHub Actions and is not evidence of stealthy filesystem access.
Low
Weak Cryptography Findings Lack Source Evidence
The reported weak cryptography locations do not contain cryptographic operations in the reviewed source context. No evidence found for MD5, SHA1, DES, RC4, or similar weak algorithm usage.
Manual review of the cited lines showed skill metadata, a kubectl describe command, and a related-skill reference. These do not implement cryptography.

Risk findings

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

Confirmed security concerns (2)

RISK-001 Medium
Mutable Third-Party Action References
The security scan examples use actions referenced with the mutable master branch. This is a supply-chain risk because future upstream changes would alter workflow behavior without review.
The lines explicitly reference third-party actions with @master. Mutable action refs are a well-known CI supply-chain risk, even though the examples are not malicious.
RISK-002 Medium
Privileged CI Command Templates
The templates include shell commands that update kubeconfig, apply Kubernetes manifests, inspect production resources, install dependencies, run tests, and deploy applications. These are expected for CI/CD, but copied workflows can execute powerful operations in user repositories.
The commands are visible in workflow examples and are appropriate for the skill purpose. Risk depends on repository permissions, runner trust, and user customization.

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
Static Command Execution Findings Are Documentation Examples
The Ruby or shell backtick detections correspond to Markdown YAML snippets and reference text, not code that the skill executes. They should be treated as workflow content that users may copy, not runtime behavior of the skill.
The reviewed file is SKILL.md and the relevant sections are fenced YAML examples or reference bullets. No executable script file or hidden runtime launcher is present in the reported file structure.

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