comfyui-gateway — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited comfyui-gateway (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Design or review a REST gateway around an existing ComfyUI server. This skill contains documentation only: no gateway application, package manifest, Dockerfile, CLI, database migrations or runnable workflow templates are bundled. Obtain the actual implementation and its version before proposing install or startup commands. The proposed gateway routes below are not native ComfyUI endpoints.
Use when designing ComfyUI job submission, authenticated result delivery, worker queues or webhook integrations. For direct ComfyUI calls, consult its native API.
A gateway can validate requests, map reviewed workflow templates, submit work to ComfyUI, persist job state and deliver authorized outputs. Fastify, BullMQ, Redis, SQLite/Postgres and S3 are possible components, not installed capabilities.
| Proposed gateway operation | Required behavior |
|---|---|
| POST /jobs | Authenticate caller; validate bounded inputs; authorize workflow; return job ID |
| GET /jobs/:id | Return only jobs accessible to this principal |
| POST /jobs/:id/cancel | Authorize cancellation; distinguish requested from confirmed cancellation |
| GET /outputs/:id/:file | Enforce ownership and path containment; never trust caller file paths |
| Workflow CRUD | Require admin authorization and audit changes |
| Health/capabilities | Expose minimal operational information without secrets |
Specify one state vocabulary, for example queued, running, succeeded, failed and canceled. Persist transitions atomically. A client timeout does not cancel server work. Define restart recovery, idempotency-key scope/expiry and retry behavior; Redis alone does not prove durability or exactly-once execution.
Native ComfyUI routes include POST /prompt, GET /history/{prompt_id}, GET /view, GET /object_info and WS /ws. Validate the pinned server's request/response shapes. Export a complete API-format workflow from ComfyUI; a two-node fragment with references to absent nodes cannot execute. Preserve numeric input types when rendering templates and reject unknown nodes/parameters.
authentication, per-principal authorization and network controls. CORS is not access control. Fail startup when required credentials are missing.
embed admin keys in browser clients or issue ad-hoc admin JWTs to fix access.
appropriate, and revalidate every redirect or disable redirects. A hostname allowlist alone does not prevent SSRF or DNS rebinding.
and durable deduplication; acknowledge only after durable acceptance.
and signed URL lifetimes. Include workflow/model/version/seed in cache identity; random-seed jobs must not accidentally reuse another generation or tenant data.
More steps usually increase time; diagnose the actual memory-failing node before promising that fewer steps solve OOM. Model, hardware and custom nodes matter.
installation, deployment, data transmission and destructive actions for approval.
User: “Put our local ComfyUI behind a job API.”
Response: “First identify the reviewed server/gateway commit, complete workflow, allowed callers and output retention. I will propose a job-state/auth contract, then test invalid inputs, cross-user job access, callback SSRF, replay, restart recovery and cancellation in an isolated deployment before exposing it.”
Read integration guidance for webhook verification and troubleshooting for bounded diagnosis.
This is a design reference, not a deployable gateway or production-security certification. No runtime/API compatibility, throughput, automatic fallback, privacy mode, included model or deployment guarantee is established by this tree. Require tests against the actual implementation before asserting those features.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.