Versioned security assessment

Report ID: SA-29B4650B

6/29/2026, 8:47:08 PM

runcomfy-cli security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
runcomfy-cli
Version
v2
Maintainer
doany-ai
Source
github.com/doany-ai/skills/tree/main/runcomfy-cli/
Coverage
1 Files scanned · 272 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Low

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.

Static analysis reported many command, network, and filesystem patterns, but the reviewed file is a Markdown skill guide for the RunComfy CLI rather than executable source code. The external command and network behavior is intentional for this CLI skill, while the weak-crypto and path-traversal alerts appear to be false positives from prose and example output. Publish with a warning because the skill can cause authenticated remote model execution, file downloads, and local token handling.

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

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

Filesystem access

May read or write local files.

Observed in 5 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 6 evidence locations

Capability review items (4)
Medium
SKILL.md:89-92SKILL.md:242-244
Authenticated Remote Model Execution
The skill is designed to run RunComfy model jobs through the CLI. This is legitimate for the skill purpose, but it sends user input to a remote API and may incur account usage or billing.
The reviewed lines explicitly document submitting JSON bodies to RunComfy and downloading remote outputs. The behavior is intentional, but it is security-relevant because it uses authenticated network execution.
Medium
SKILL.md:65SKILL.md:71SKILL.md:251
Local Token Storage and Secret Handling
The authentication flow stores an API token in a local config file or accepts RUNCOMFY_TOKEN from the environment. This is expected for a CLI, but token exposure would give access to the user account.
The token storage path and environment variable are explicitly documented. The skill also warns not to log or commit the token, which reduces but does not remove the risk.
Medium
SKILL.md:121SKILL.md:154-155SKILL.md:258
Remote Output Downloads to Local Paths
The CLI downloads generated files to the current directory or a user-selected output directory. This can write large remote outputs to disk and should be used with controlled paths.
The file-write behavior is clear from the command options and download description. A documented 2 GiB cap reduces disk-fill risk but does not eliminate local file-write concerns.
Low
SKILL.md:32-45SKILL.md:170-175SKILL.md:192-198SKILL.md:215-222
Markdown Command Examples Trigger Static Command Alerts
Many external command alerts are from fenced examples such as install commands, status polling, shell loops, and jq usage. They are documentation examples, not hidden executable code inside the skill file.
The commands are visible Markdown examples and the skill declares a narrower Bash(runcomfy *) tool scope. Some examples still require user care if copied into a shell.

Risk findings

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

Confirmed security concerns (1)

RISK-001 Low
SKILL.md:114
Path Traversal Alert Is Example URL Text
The path traversal alert points to an abbreviated output URL containing an ellipsis, not a filesystem traversal or path join operation.
The cited line is an example hosted result URL in CLI output. No local path traversal logic is present in the reviewed skill file.

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
SKILL.md:5-6SKILL.md:224
Weak Cryptography Alerts Are False Positives
The weak cryptographic algorithm alerts at the cited lines do not correspond to cryptographic code. The cited content is metadata description and an exit-code section heading.
Manual review found no hashing or encryption operation at these locations. The static scanner appears to have matched incidental text, not executable crypto usage.

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