Integrity Status

Integrity Status is a self-audit node that reports whether ComfyUI-CustomNodePacks is installed in a healthy state. Custom node installs rot in unglamorous ways: a file gets half-updated by a botched git pull, a background scan flags a suspicious sibling custom node, a dependency check fails, or your copy drifts from what the author shipped. This node runs the pack's integrity scanner and hands you a report string so you find out deliberately instead of through a mysterious failure later.

It's part of ComfyUI-CustomNodePacks, the ~72-node pack from Code2Collapse (Likhith-24, active on r/comfyui), in the C2C/Diagnostics category - and it's the pack auditing itself, which is a rare level of paranoia for this ecosystem.

How it works

The scanner (in the pack's integrity_guard.py) does three kinds of checks:

• Checksum drift - a SHA-256 of every .py file in the pack compared against a baseline (third_party/checksums.json). Drift means your files differ from the shipped state - the classic sign of a partial update or local edit you forgot about.
• Pip check - whether the pack's declared dependencies are present and consistent (pip_check_ok).
• Suspicious-node scan - scans other custom nodes for risky patterns, which matters in an ecosystem where a malicious node is functionally equivalent to running a malicious executable on your machine.

The node itself returns a report (STRING): a head line with events=… pip_check_ok=… checksum_drift=… plus up to 20 event lines describing anything the scan flagged. The trigger_rescan boolean is the interesting control - set it true to force an immediate rescan instead of reading the cached result, which is what you want right after an update or when you suspect a problem.

How to read it

• pip_check_ok=true and events=0 - healthy. Move on.
• checksum_drift events - your installed copy differs from baseline. Almost always "I edited a file" or "the update was interrupted." A git pull / reinstall clears it.
• Scan events about another custom node - read them. The scan is flagging something it found risky; in this ecosystem, a quick look beats trusting an anonymous repo.

Installing it

Ships in ComfyUI-CustomNodePacks. ComfyUI Manager → search "CustomNodePacks", or:

cd ComfyUI/custom_nodes
git clone https://github.com/Code2Collapse/ComfyUI-CustomNodePacks.git

The pack's requirements.txt mentions pipdeptree for the integrity guard, but the current scanner implementation no longer needs it - it does its own dependency and checksum checks, so don't install extras for this. Just the pack's standard deps (opencv-python>=4.7.0, scipy>=1.10.0) if missing. Restart ComfyUI.

Common issues

• "integrity scan running…" - the scan runs in the background and the node returns this while it works. Wait a moment or set trigger_rescan true and re-run; the scan itself is fast (checksums of a few dozen files).
• Checksum drift after an update - expected mid-update; a full reinstall brings the baseline back in line. Don't panic unless it persists after a clean git pull.
• Events but you haven't touched anything - that's the point of the scan. Read the event lines; they name the file and kind, which is far more useful than a silent future crash.

The honest take: most ComfyUI users will never run this node, and the pack works fine without it. But given how many "it just broke after the update" threads the ecosystem produces, a node that tells you what drifted, in one string, is a genuinely thoughtful thing to ship.