This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 1.0.1 instead.
laidline-comfyui
ComfyUI custom node LaidlineSaveImage ("Save Image (Laidline: sign + watermark)", category image/laidline). It replaces
ComfyUI's Save Image node: each image in the batch is watermarked with TrustMark, signed with a C2PA manifest, logged to
the evidence sinks, and written to ComfyUI's output directory.
Modes
- Remote (sidecar): set
LAIDLINE_URLto the Laidline server (andLAIDLINE_API_KEYif it requires one). Takes precedence when both are set. - Embedded: set
LAIDLINE_CONFIGto alaidline.yaml; marking runs in the ComfyUI process.
With neither set, the node fails with Laidline: set LAIDLINE_URL (sidecar) or LAIDLINE_CONFIG (embedded).
Inputs and outputs
images(IMAGE): the batch to save.filename_prefix(STRING, defaultlaidline): as in Save Image; may include a subfolder.format:png,jpegorwebp.request_id(STRING, optional): recorded in the evidence log.
The node passes images through unchanged. Its ui output lists the saved files under images and, under laidline,
one entry per file with asset_id, manifest_id and warnings (for example watermark_skipped:too_small when the
short side is under watermark.min_side_px, default 128). A marking failure is raised as a RuntimeError shown on the node.
There is no LaidlineMarkImage node: a marked tensor cannot carry a C2PA manifest and any downstream node re-encodes it,
so only the saved file can be signed.
Installation
Copy or symlink laidline_comfyui into ComfyUI's custom_nodes/ and pip install laidline[image]. The pack uses relative imports only, so ComfyUI's custom-node loader can import it from custom_nodes/.
Proven against a real ComfyUI v0.37.0 on CPU (remote mode, PNG and JPEG: watermark, Trusted manifest and evidence
entry with route: comfyui:LaidlineSaveImage). Setup and the full guide:
https://laidline.com/docs/integrations/comfyui.
Metadata
Release files for laidline-comfyui 1.0.0
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 |
|---|---|---|---|---|
| laidline_comfyui-1.0.0.tar.gz | 10.7 kB | Without provenance | Details for laidline_comfyui-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| laidline_comfyui-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for laidline_comfyui-1.0.0-py3-none-any.whl |
Total release size: 22.8 kB
Release files / laidline_comfyui-1.0.0.tar.gz
| Download URL | laidline_comfyui-1.0.0.tar.gz |
|---|---|
| Size | 10.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b31dd9c5028796dde10e3f9756627c2c18eaf4f892f94892354281cdbddb8b0
|
|
BLAKE2b-256 checksum How to use checksums |
9727bff3f04a558cfd7ed22297d60273a601fcba26428696e7bde990cd306198
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / laidline_comfyui-1.0.0-py3-none-any.whl
| Download URL | laidline_comfyui-1.0.0-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
54ccbe12a6ea52aa041c1a4192e8d8a30b77a3af9ab4ad9460bd5f2a54452461
|
|
BLAKE2b-256 checksum How to use checksums |
2edb8f5ee7106057658ce0be19aceb178173cb9c7f03f0f791d43026a72b07dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Security for laidline-comfyui 1.0.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.