Versioned security assessment

Report ID: SA-97067D94

7/5/2026, 7:52:53 PM

gpt-image-2 security assessment v3

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
gpt-image-2
Version
v3
Maintainer
runcomfy-com
Source
github.com/runcomfy-com/skills/tree/main/gpt-image-2/
Coverage
1 Files scanned · 212 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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 review confirmed documented RunComfy CLI execution, a POST to the RunComfy Model API, and local RunComfy token storage. Most other detections are Markdown formatting, example placeholders, REST path abbreviations, or sample prompts with no execution behavior. No prompt injection or covert data exfiltration intent was found.

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

14 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 6 evidence locations

Filesystem access

May read or write local files.

Observed in 4 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 41 evidence locations

Capability review items (14)
High
SKILL.md:207
Hidden file in home directory
- **Token storage**: `runcomfy login` writes the API token to `~/.config/runcomfy/token.json` with m
Line 207 documents RunComfy token storage at a hidden home-directory path. Credential storage is security-sensitive even when owner-only permissions are used.
Medium
SKILL.md:9-10
Ruby/shell backtick execution
(Flux 2 / Nano Banana Pro / Seedream) instead. Calls `runcomfy run
The front matter says the skill calls the local RunComfy CLI endpoints. This is expected behavior, but it is real external command use that sends prompts to a remote service.
Medium
SKILL.md:10
Ruby/shell backtick execution
openai/gpt-image-2/text-to-image` or `/edit` through the local
The front matter names the RunComfy CLI endpoint used by the skill. This confirms external command use, even though the text is documentation rather than executable code.
Medium
SKILL.md:24-26
Ruby/shell backtick execution
```bash
The fenced setup example runs npx to add the skill globally. Remote global installation is legitimate setup, but it is a real external command risk.
Medium
SKILL.md:45-46
Ruby/shell backtick execution
1. **RunComfy CLI** — `npm i -g @runcomfy/cli`
The prerequisite instructs users to install the RunComfy CLI globally with npm. Global package installation is a real external command with supply-chain impact.
Medium
SKILL.md:46-47
Ruby/shell backtick execution
2. **RunComfy account** — `runcomfy login` opens a browser device-code flow.
The prerequisite instructs users to run runcomfy login. This is a legitimate authentication command, but it invokes a local CLI and starts a credential flow.
Medium
SKILL.md:74-78
Ruby/shell backtick execution
```bash
The text-to-image example invokes runcomfy run with user prompt input and an output directory. This is expected, but it is real local command execution.
Medium
SKILL.md:82-89
Ruby/shell backtick execution
```bash
The edit example invokes runcomfy run with a prompt and image URL list. This is expected, but it executes a local CLI and submits data to RunComfy.
Medium
SKILL.md:93-100
Ruby/shell backtick execution
```bash
The multi-reference edit example invokes runcomfy run with external image URLs. This is expected, but it is real CLI execution with remote service submission.
Medium
SKILL.md:106-109
Ruby/shell backtick execution
```bash
The pipe-friendly example runs runcomfy and pipes output to jq. This is a real shell pipeline, although its purpose is limited to extracting a request id.
Medium
SKILL.md:194-195
Ruby/shell backtick execution
1. The skill invokes `runcomfy run openai/gpt-image-2/<endpoint>` with a JSON body matching the sche
The How it works section states that the skill invokes runcomfy run with a JSON body. This confirms the skill depends on external CLI execution.
Medium
SKILL.md:207
Ruby/shell backtick execution
- **Token storage**: `runcomfy login` writes the API token to `~/.config/runcomfy/token.json` with m
The security section documents runcomfy login as a command with credential storage side effects. This is legitimate, but still a real external command risk.
Medium
SKILL.md:207
Hidden file access
- **Token storage**: `runcomfy login` writes the API token to `~/.config/runcomfy/token.json` with m
Line 207 documents access to a hidden RunComfy token file. The path is legitimate, but it stores an API token and should remain protected.
Low
SKILL.md:195
Hardcoded URL
2. The CLI POSTs to `https://model-api.runcomfy.net/v1/models/openai/gpt-image-2/<endpoint>` with th
The How it works section documents an outbound POST to the RunComfy Model API with the user bearer token. This is expected, but it is real network transmission.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

Remediation

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

  1. FIX-001
    High
    Local credential storage
    Keep the token file owner-only, never print it, and document RUNCOMFY_TOKEN as the preferred CI option.
  2. FIX-002
    Medium
    External CLI execution
    Ask for user confirmation before running RunComfy CLI commands. Keep prompt and image inputs structured, and avoid shell interpolation.
  3. FIX-003
    Low
    Outbound model API submission
    Tell users that prompts, image URLs, and bearer tokens are sent to RunComfy. Warn against submitting sensitive private assets.

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