Is Viggle/Meridian safe to load?
CyberXYZ rates Viggle/Meridian HIGH, driven by torch 2.9.1 · GHSA-63cw-57p8-fm3p. It depends on 133 tracked packages, and 9 carry advisories. It does not require trust_remote_code. A mixed serialization signal is recorded for it; the model_load_safety tool gives the per-file verdict.
HIGHDeclared install pins version-matched high/critical advisories: torch 2.9.1
5 more findings on this model.
- Author
- Viggle
- Task
- video-to-video
- Loader
- diffusers
- License
- other
- Downloads
- 0
- Remote code
- not required
41 direct, 31 with findings, 120 reachable
| Package | Evidence | Advisories | Worst |
|---|---|---|---|
| torch | direct, install | 13 | HIGH |
| pillow | direct, install | 147 | none pinned |
- HIGHrisk level raised (medium to high)2026-11-04
Is Viggle/Meridian safe to load?
CyberXYZ does not call a model safe in absolute terms. It rates Viggle/Meridian HIGH, driven by torch 2.9.1 · GHSA-63cw-57p8-fm3p. That covers its dependencies and how it loads, not every file it ships, so treat any check that did not run as unverified and check the exact files before you load them.
What does Viggle/Meridian depend on?
CyberXYZ tracks 133 dependencies for Viggle/Meridian, 41 of them direct. 9 carry advisories. They include torch and pillow. A free account lists all of them.
Does Viggle/Meridian run code when it loads?
HuggingFace does not mark Viggle/Meridian as requiring trust_remote_code. That says nothing about the format of its weight files, which model_load_safety checks per file.
How do I check Viggle/Meridian before loading it?
Run the xyz MCP tool model_load_safety on Viggle/Meridian to get a verdict on its weight files before you load them, or search it in CyberXYZ Check at https://cyberxyz.io/check?q=Viggle%2FMeridian.
Risk computed 2026-11-14 at 10:58 UTC. Dependencies come from the model's requirements, its declared loader and the code it ships; advisories from NVD, GHSA and OSV.