What security and quality rules must ComfyUI custom nodes meet to be published on the Comfy Registry, and what does that guarantee users?

Comfy docs (captured 2026-10-23): the Comfy Registry backs ComfyUI-Manager; published versions are immutable and semantically versioned, and can be deprecated with a message shown to users. The overview says all nodes will be scanned for malicious behaviour (e.g. custom pip wheels, arbitrary system calls). Published security standards prohibit eval/exec (RCE risk when workflows pass user inputs), runtime pip installs via subprocess (dependencies must go through Manager to reduce supply-chain risk), and code obfuscation; base standards require community value (no impersonation/malicious behaviour, limited self-promotion), not interfering with other nodes, legal compliance, maintained/documented functionality, and clearly distinct forks. Practical reading: Registry publication plus Manager security levels (C3-B337-01) reduces but does not remove risk; ComfyUI's own threat model still treats every custom node as trusted code you choose to run, and Manager's git-URL/pip installs bypass Registry versioning. Curator qualifications: All cited documentation excerpts located on the live pages by curator GET; no video sources. Scanning method/results still not documented (consistent with C3-B049-G17-03). Limitations: Scanner coverage and enforcement record not documented on these pages ("will be scanned"). Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://docs.comfy.org/registry/standards.md",
      "note": "Security Standards: eval/exec; subprocess for pip install; Code Obfuscation; overview para \"Node Security\"; FAQ"
    },
    {
      "url": "https://docs.comfy.org/registry/overview.md",
      "note": "Security Standards: eval/exec; subprocess for pip install; Code Obfuscation; overview para \"Node Security\"; FAQ"
    }
  ]
}