Versioned security assessment

Report ID: SA-A123277D

6/30/2026, 1:02:39 AM

expo-cicd-workflows security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
expo-cicd-workflows
Version
v3
Maintainer
expo
Source
github.com/expo/skills/tree/main/plugins/expo-deployment/skills/expo-cicd-workflows/
Coverage
3 Files scanned · 288 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

3 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 high-risk patterns, but the apparent weak-crypto and shell-backtick detections are false positives after review. The confirmed risks are legitimate but elevated: helper scripts fetch official Expo workflow resources, read workflow files, write a local cache, and the skill instructs agents to run Node-based validation commands.

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

3 Files scanned · 288 Lines analyzed

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

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Observed in 3 evidence locations

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 3 evidence locations

Risk findings

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

Confirmed security concerns (3)

RISK-001 Medium
scripts/fetch.js:22-27scripts/validate.js:13-17SKILL.md:22-34
Network Fetching of Workflow Reference Data
The helper scripts fetch the current Expo workflow schema and documentation from Expo-controlled URLs. This is legitimate for the skill purpose, but it introduces network dependency and remote-content trust considerations.
The fetch call and fixed schema URL are directly visible, and the skill explicitly requires fetching these resources. The URLs are official Expo resources, so this is a legitimate elevated risk rather than malicious behavior.
RISK-002 Medium
SKILL.md:4SKILL.md:17-20SKILL.md:81-85
Agent-Run Node Helper Scripts
The skill allows Bash execution for Node commands and instructs agents to run helper scripts and install script dependencies. This is expected for workflow validation, but it expands execution risk compared with documentation-only skills.
The allowed tool declaration and command examples are explicit. The commands target local helper scripts, so the risk is from permitted execution scope rather than evidence of command injection.
RISK-003 Low
scripts/fetch.js:12-15scripts/fetch.js:61-63scripts/validate.js:27-28
Local Cache and Workflow File Access
The fetch helper creates a local cache and writes fetched data, while the validator reads user-specified workflow files. This matches the documented purpose and does not show evidence of unauthorized file access.
Filesystem reads and writes are directly present. The paths are either the cache directory or user-provided workflow files for validation, making the observed behavior expected and limited.

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 (3)
Low
scripts/fetch.js:37scripts/fetch.js:99-103scripts/validate.js:34scripts/validate.js:50scripts/validate.js:60-62SKILL.md:15-20SKILL.md:42SKILL.md:58-65SKILL.md:73-75SKILL.md:81-85
Static Backtick Command Findings Are False Positives
The reported backtick findings are JavaScript template literals, Markdown code fences, inline code, or console output strings. No Ruby backtick execution or shell command interpolation was found in the reviewed files.
The reviewed contexts show formatting or JavaScript strings, not shell execution syntax. No dynamic child_process, eval, or Ruby-style backtick execution was present in these locations.
Low
scripts/fetch.js:49-51
Static Weak-Crypto Findings Are False Positives
The only cryptographic API usage hashes a URL with SHA-256 to create a cache filename prefix. SHA-256 is not weak in this context and is not used for passwords, signatures, or encryption.
The code clearly uses createHash with sha256 only for deterministic cache naming. There is no security-sensitive cryptographic decision or weak algorithm evidence at this location.
Low
SKILL.md:1-93
No Prompt Injection Attempt Found
No text was found that claims system authority, asks the evaluator to ignore instructions, or attempts to override the security review process.
The reviewed skill text contains task instructions for Expo workflow assistance, not evaluator-directed override language. This assessment is limited to the three audited files.

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