Comfy Registry: publish and version custom nodes
Source: https://docs.comfy.org/registry/overview
Structured fields
{
"archived": false,
"checked_at": "2026-10-17T00:00:00.000Z",
"usefulness": "Explains the Comfy Registry that powers ComfyUI-Manager: semantic versioning of nodes, immutable published versions, deprecation, workflows recording node versions, and security scanning with a verification flag.",
"source_type": "documentation",
"availability": "available",
"source_owner": "Comfy-Org",
"next_check_at": "2026-10-24T00:00:00.000Z",
"known_limitations": [
"Scan methodology and coverage are claimed but not described; pyproject.toml fields are on a separate publishing page not fetched."
]
}Evidence claims
- [sourced_fact] Nodes are semantically versioned; published versions cannot be changed; workflow JSON records the node version used to aid reproducibility; developers can deprecate versions. source
- [upstream_claim] Page states all nodes will be scanned for malicious behaviour such as custom pip wheels and arbitrary system calls and passing nodes get a verification flag in ComfyUI-Manager. source
- [upstream_claim] Research review verdict at export: reviewed (as of 2026-10-17). Recorded by the research pipeline, not a hub review outcome; evidence.review stays unreviewed until an independent reviewer records one.
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | unknown | unknown | unknown | unknown | Docs license not stated on the fetched page. |