comfy-dev
Developer tools for ComfyUI custom nodes.
Installation
pip install comfy-dev
Usage
# Initialize in your custom node project
cd my-custom-node
comfy-dev init
# This creates comfy-dev.toml and installs git pre-commit hooks
# Workflow files are automatically laid out on commit
# Manual layout
comfy-dev layout workflows/my_workflow.json
comfy-dev layout # Layout all workflows from config
Configuration
comfy-dev.toml:
[layout]
algorithm = "sugiyama"
rank_sep = 200 # Spacing between columns
node_sep = 150 # Spacing between nodes in same column
[layout.paths]
workflows = ["workflows/*.json"]
[hooks]
pre_commit = ["layout"]
Commands
comfy-dev init- Create config and install hookscomfy-dev layout [files...]- Auto-layout workflow filescomfy-dev hook install- Install git hookscomfy-dev hook uninstall- Remove git hooks
Metadata
Release files for comfy-dev 0.0.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| comfy_dev-0.0.10.tar.gz | 10.7 kB | With provenance | Details for comfy_dev-0.0.10.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| comfy_dev-0.0.10-py3-none-any.whl | Python 3 | none | any | Details for comfy_dev-0.0.10-py3-none-any.whl |
Total release size: 24.3 kB
Release files / comfy_dev-0.0.10.tar.gz
| Download URL | comfy_dev-0.0.10.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2f73a3084d3f08130acbecaf48233d209dab90fe6a01ed199e7caaf88091714
|
|
BLAKE2b-256 checksum How to use checksums |
1be5986797857f9405bdc2ead26accc48088364f5db0d467382f906215e00267
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 12, 2026.
Transparency logRelease files / comfy_dev-0.0.10-py3-none-any.whl
| Download URL | comfy_dev-0.0.10-py3-none-any.whl |
|---|---|
| Size | 13.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
31c40adb1621794b89e3037e46085b15e2bb17439bf55d39f6cea4b787b4d85b
|
|
BLAKE2b-256 checksum How to use checksums |
1606da1f75f9fd9a9a7771da459a42ab475bfaed6bf1f21433a6d34c8f72f7f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 12, 2026.
Transparency logSecurity for comfy-dev 0.0.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for comfy_dev-0.0.10.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.