HF VANISHED

Disabled, deleted, auth-required/private after prior public evidence, or model files removed.

The final confirmed public profile is frozen before a later disappearance: Hub downloads/likes, task/type, architecture, parameters when exposed, format, quantization metadata, license and revision. Missing historical fields stay unknown.

A previously unavailable, gated or stripped model is observed publicly accessible again. Restoration records the state change, not why it happened.

The unauthenticated Hub API now returns 401/403 after prior public evidence. That response alone does not prove whether the repo was made private or deleted.

A public model becomes gated or otherwise newly access-restricted.

Official, primary source, corroborated or reported reasons require public source links. Otherwise the cause remains unknown.

Bounded captures of discussions, discussion events, commits, model-card hashes and a pre/post timeline can survive after the live repo changes state.

When the Hub exposes them, manifests retain Git OIDs, LFS SHA-256 and Xet hashes plus a deterministic manifest root. Hash identity is proof of bytes/metadata, not proof that HF Vanished hosts them.

Base-model relationships are recorded only when the Hub model-card metadata explicitly declares them. Name similarity is never treated as provenance.

Temporal, same-owner and same-family clusters help researchers notice patterns. They do not prove mass reporting, coordination, censorship, legal action or government intervention.

Pirate Face reports a torrent. Protected means HF is still reachable; Rescued means HF Vanished sees the source as gone/restricted while a P2P copy is known.

No active Pirate Face torrent is known yet. “No known copy” only means this tracker has not verified one, not that the bytes do not exist anywhere.

Brief changes under 24 hours and models never observed public are excluded from automatic disappearance events.