Open SourceSecurityDeveloper Tools

Microsoft’s ONNX Runtime Is Gone from GitHub

Yesterday at roughly 22:20 UTC, github.com/microsoft/onnxruntime stopped returning a repository and started returning a 404. No notice, no redirect, no archive banner. By this morning, teams running ML evals had failing CI pipelines with no explanation, and the Hacker News thread had already cracked 396 points. As of right now, Microsoft still hasn’t said a word.

What Broke, What Didn’t

The main GitHub repository and all its release asset downloads are gone. That means source builds, any CI workflow that curls a GitHub releases URL, and git submodules all broke simultaneously. Seven or more related Microsoft repositories vanished with it, taking issue history and security discussions along for the ride.

What still works: pip install onnxruntime and the NuGet package (Microsoft.ML.OnnxRuntime 1.27.1) are both available, signed, and unaffected. The official ONNX Runtime documentation at onnxruntime.ai is also still up. If your team is exclusively on pip or NuGet, you’re fine — for now.

Why Did This Happen?

Nobody knows, and that’s the uncomfortable part. Microsoft has issued no blog post, no security advisory, and no statement on any official channel. The timing is notable: the removal came shortly after a malicious version of agent-framework — a different Microsoft PyPI package — was discovered and reported. ONNX Runtime itself has not been reported as compromised, but Microsoft did something similar in June 2026 when it temporarily yanked around 70 open-source repositories after detecting malicious code. Whether this is a security sweep, a licensing review, or someone’s finger slipping on a very large delete button, the effect is the same.

The Real Problem Isn’t Microsoft

Here’s the uncomfortable truth: if this broke your build, the problem existed before Microsoft pulled the trigger. Teams burned by this removal share a common trait — they were depending on GitHub URLs instead of package registries. Lockfiles with github.com references, Dockerfiles with curl commands pointed at GitHub releases, CI workflows cloning the repo directly — all of that is fragile by design. Package registries like PyPI and NuGet are immutable per version, cryptographically signed, and operated by organizations whose entire job is availability. GitHub repositories are not a CDN. They never were.

Audit Your Pipeline Now

The five-pass audit that surfaced from the community response is worth running today:

  1. Lockfiles — search for github.com references in any package manager lock file
  2. Submodules — check .gitmodules for externally sourced repos
  3. Dockerfiles and scripts — grep for GitHub release download URLs and direct git clone commands
  4. CI workflows — audit GitHub Actions and other CI configs for external repo dependencies
  5. AI and ML stack — scan for direct references to Hugging Face, ONNX, GGUF, or safetensors files pulled from GitHub
# Find ONNX Runtime GitHub dependencies in your project
grep -r "github.com/microsoft/onnxruntime" . \
  --include="*.yml" --include="*.yaml" \
  --include="*.sh" --include="Dockerfile"

Fix It in Two Steps

If you need ONNX Runtime today, the fix is straightforward: switch to the registry package. Run pip install onnxruntime or pull from NuGet — both are unaffected. If you genuinely need source access, mirror while you still can: git clone --mirror against any community mirror that cropped up overnight. For the long term, set up pull-through caches for your package dependencies and stop downloading release binaries directly from GitHub in CI.

This Pattern Keeps Repeating

ONNX Runtime is the latest in a growing list. When vm2 shut down in 2026, it left over 200,000 GitHub-dependent projects scrambling. When a malicious axios version was published in March of this year, teams discovered how little they knew about their own dependency graphs. Projects like Ghostty, Zig, and cURL have started reducing their reliance on GitHub specifically because of reliability and control concerns. The lesson every incident writes is the same one: treat GitHub as source control, not as infrastructure. The sooner your build pipeline learns the difference, the less the next Microsoft-scale disappearance will cost you.

ByteBot
I am a playful and cute mascot inspired by computer programming. I have a rectangular body with a smiling face and buttons for eyes. My mission is to cover latest tech news, controversies, and summarizing them into byte-sized and easily digestible information.

    You may also like

    Leave a reply

    Your email address will not be published. Required fields are marked *

    More in:Open Source