The dispute is upstream.

What is “distillation”?

Using a competitor's public API at scale to generate training data, then fine-tuning your own model on that data. The accusation is that Chinese labs ran thousands of accounts against Claude / GPT-4 to bootstrap their own models cheaply.

Who's named

Anthropic has publicly identified DeepSeek, Moonshot (Kimi), and MiniMax. OpenAI has separately accused DeepSeek of copying its technology. The labs deny it. The dispute is unresolved.

What the WH memo does

Commits the executive branch to share threat info with US AI firms, develop best practices, and “explore” accountability mechanisms. It does not propose a ban on running open-weight Chinese models, and it doesn't claim the models themselves are unsafe.

Notice what's not in any of this: a claim that the released GGUF weights are backdoored, a claim that running them locally exfiltrates data, or any technical safety advisory. The dispute is about how the models were built, not what they do after you download them.

Three concerns. Two are zero. One is yours.

Technical safety: zero

GGUF and SafeTensors are data formats, not executable code. Loading a model in Ollama, llama.cpp or LM Studio doesn't run code from the model's author. The historical exception — Python pickle (.pt) — isn't how local runtimes ship models in 2026.

Privacy: zero

Ollama's daemon runs on 127.0.0.1. It downloads weights on `ollama pull`, then runs inference on-device. No prompts, tokens or telemetry leave your Mac during normal use. Verify yourself with Little Snitch, tcpdump, or DevPulse's port monitor.

Reputational: yours

Some teams won't use models trained via disputed methods, regardless of runtime safety. That's a values call. The catalog labels every model with its lab and license so you can apply your own filter — DevPulse takes no position.

Provenance, license, privacy posture — visible.

Lab on every row

Each model in Can I Run? shows its origin lab inline: Meta, Mistral AI, Alibaba, DeepSeek, Google, Microsoft. Pick what fits your stance.

License on every row

Apache 2.0, MIT, Llama Community, Qwen Research — license shows in the row's expand panel. If you need a model for commercial use, the license is the first filter, and it's right there.

Privacy note

A one-line reminder above the model list: weights run fully offline once downloaded; weights don't execute code; no data leaves your Mac. Same in the popover and on the web.

Want the source of truth? The model catalog is a JSON file shared between the macOS app and this website — same lab, same license, same RAM estimates in both places. Browse the full list in Can I Run AI Models? →

If you're running these models locally.

  1. Pull from Ollama or a known mirror.The risk you should care about is supply-chain — a tampered weights file from an unknown source. Ollama's library and Hugging Face's verified org accounts (DeepSeek, Alibaba, Meta) publish digests. Verify or trust the source you'd trust for any binary.
  2. Stay on GGUF / SafeTensors. If a model is only distributed as a Python pickle, treat it as you would any executable from the internet — sandbox it or skip it.
  3. Confirm offline behavior once. Load the model, fire a prompt, watch network traffic with Little Snitch or tcpdump. You'll see no outbound traffic. After that you don't have to keep checking.
  4. Pick by license, not just by capability. If you ship code that touches output from a model, the license determines whether you can use it commercially. Apache 2.0 and MIT are the most permissive; Llama Community and Qwen Research have more restrictions.
  5. Keep the cloud + local mix flexible. Local models cover most of the volume, cloud handles the hardest tasks. See the case for hybrid local + cloud →

Source notes.

Provenance and privacy, in the menubar.

DevPulse shows lab, license and runtime status on every model — no editorial, just facts.

Download for macOS

macOS 14+ · Apple Silicon & Intel · Free during launch