Nodes/IndexTTS 2.5 · T8star-Aix/IndexTTS 2.5 检查更新 · T8star-Aix
ComfyUI Node

IndexTTS 2.5 检查更新 · T8star-Aix

A version check that only ever talks

By T8mars·Created about a month ago·Updated 5 days ago· 52
IndexTTS 2.5 检查更新 · T8star-Aix
    • 更新检查 JSON
    • 检查摘要
    refresh_token0
    timeout_seconds12

    This pack is aggressively pinned: it runs a fixed IndexTTS code revision, a fixed official model revision, and its own versioned node code. That's mostly a good thing - reproducibility, no surprise breakage when upstream moves - but it creates a new problem: how do you know when upstream has moved? 检查更新 (check update) answers that, and the whole design is summed up in one constraint: it reports and never touches anything.

    Run it, and it compares three things against three fixed endpoints: the latest commit on the official index-tts/index-tts repo, the current state of the official IndexTeam/IndexTTS-2.5 model on Hugging Face, and this node's own published version (read from pyproject.toml on GitHub). No downloads, no file overwrites, no auto-update, no code execution. It's a read-only status probe you trigger manually - which is exactly what you want from a pack that treats every network operation as something the user must initiate.

    The inputs (there are barely any)

    • refresh_token - bump this integer to force a fresh check. It's a rerun trigger, not a value that does anything on its own.
    • timeout_seconds - per-request timeout, default 12. Raise it on slow networks; the three requests run sequentially against their endpoints.

    That's the whole input surface. If a node could have zero inputs this would be close.

    Outputs

    • report - the full JSON: each endpoint's status, the versions found, and whether the node is behind upstream code or model.
    • summary - a one-liner you can drop into a text node: "official code moved, model unchanged, node version current" and the like.

    Security, and why it's mentioned in the README

    The registry security scan flagged this pack's network behavior more than once, and the fix is visible in the code: the update check only talks to three hard-coded official endpoints, disables cross-site redirects, caps each response at 1 MiB, and refuses to make requests anywhere else. That's the right posture for a node that touches the network at all - and it's why this is the only thing in the pack that phones home without you having already downloaded something.

    Installing and the honest caveat

    Standard install: ComfyUI Manager → IndexTTS 2.5 · T8star-Aix, or git clone https://github.com/T8mars/comfyui-indextts25-t8.git into custom_nodes/, restart. It needs internet at run time and nothing else - no model, no audio.

    One caveat before you start treating it as an update button: it tells you what changed, not whether you should change anything. IndexTTS upstream moving its main branch doesn't mean this pack is broken; the pack pins a revision for a reason. The useful signal is drift over time - code and model both moving while your node version stays flat is when you should go read the changelog and decide whether a manual git pull + re-download is worth it. When you do pull, don't forget the model directory is separate from the node directory; the check won't move your weights for you.

    CategoryT8star-Aix/Audio/IndexTTS 2.5

    Inputs (2)

    NameTypeDefaultDescription
    refresh_tokenINT00–1000000
    timeout_secondsFLOAT123–60

    Outputs (2)

    NameTypeDescription
    更新检查 JSONSTRING
    检查摘要STRING