ligsp: the LIGSP checker

Checks the image-generation servers and model folders you name against the Local Image Generation Security Profile (profile.md). It is read-only, and it contacts only the places you point it at.

ligsp check http://127.0.0.1:8188                      # a ComfyUI
ligsp check http://127.0.0.1:7860 --models D:\models   # A1111 / Forge and a model folder
ligsp check http://127.0.0.1:3000 --redact             # a report you can share
ligsp check --private C:\latentry                       # who can read Latentry's settings and keys
ligsp check http://127.0.0.1:3000 --follow              # Latentry, and every backend it is set up to use

Common default ports: ComfyUI 8188, Comfy Desktop 8000, A1111 / Forge 7860, Latentry 3000, InvokeAI 9090, SwarmUI 7801. It tries no port you did not name.

What it recognises

ComfyUI (and ComfyUI-Manager), AUTOMATIC1111 / Forge, InvokeAI, SwarmUI, Latentry and its engine, and other servers on Latentry's backend API. It checks any other web server with the general checks.

What it checks

Exit code 0 when nothing failed, 1 when something failed, 2 for a usage error. --json FILE (or -) writes the same report as JSON.

What it does not do

• It sends only GET, HEAD and OPTIONS, only to a fixed list of endpoints known to change nothing, with no query strings, to the URLs you give and to the same port on this computer's own addresses. One function sends every request, and it refuses anything else (transport.py). A safe method alone is not enough: some servers act on a GET (ComfyUI-Manager releases from 2024 removed and restored snapshots on one). It never queues a job, uploads a file or changes a setting.
• It reads only the fields it needs. ComfyUI's /system_stats also lists the server's command line; that is discarded, never kept or shown.
• With --follow it reads a hub's backend list (Latentry's /api/settings, which answers only on the computer the hub runs on) and keeps only each backend's URL. Folders, model names and the rest are discarded, and the backends' own backends are not followed.
• In model folders it opens only .safetensors files, and only to read their header. It follows no links out of the folder.
• For private files it reads only their permissions: the mode, or on Windows the access list, through the Windows API and compared by account ID (SID), so it works in any system language.
• It sends no telemetry and checks for no updates, and it writes no file unless you ask (--json FILE).
• A pass means these checks found no problem, not that the setup is safe.

Standard library only (Python 3.10+). Tests: pytest in this folder, with src on the path.