ONNX Runtime Disappeared From GitHub. The Packages Still Install.

ONNX Runtime has disappeared from GitHub. Not archived, not renamed, not moved. Gone. The address github.com/microsoft/onnxruntime returns a 404, and so does the address for its companion repositories. I checked at 00:04 UTC on 18 November 2026, and again at 00:18. Both times the same answer: not found.
The repository was not a small one. Nine days ago it showed 22,267 stars, 4,428 forks, 16,124 commits and 90 releases, going back to November 2018. It is the home of the inference engine behind a large share of the machine-learning models running in production: inside Office, Bing and Visual Studio, according to Microsoft's own pages, and inside thousands of other projects that list it as a dependency. The thread that surfaced the disappearance, posted on Hacker News at 23:18 UTC on 17 November by a user whose team's evaluation pipelines had started failing that morning, now sits at 41 points with two comments and no answer. "Does anyone know why or how a repository with 22k stars just went dark?" Nobody there knew.
The first thing to check with a disappearance like this is whether the whole neighbourhood went with it. It did not. Microsoft's other large repositories — VS Code, TypeScript, the Windows Terminal — all answer normally. GitHub's own status page says all systems are operational. This is not an outage, and it is not GitHub having a bad night. It is specific to the ONNX Runtime family: the main repository, the generative-AI repository, the inference-examples repository and the training-examples repository all return 404. Four repositories, one project, gone together.
The second thing to check is what still works, because a repository is not the whole project. The project's own site, onnxruntime.ai, loads fine, and its documentation pages answer normally. The Python package is still there: version 1.32.0 is the latest on PyPI, and I downloaded the wheel, 27.8 MB, straight from the package index, no trouble. The .NET package is still there too, with 1.32.0 the latest on NuGet. If your build installs ONNX Runtime from a package index, as most builds do, nothing broke this morning. Your next install will work exactly like your last one.
So what actually happened? Honestly, nobody outside Microsoft knows yet, and the two comments on the Hacker News thread are guessing: one suggests a supply-chain attack, another jokes that Microsoft is taking a lesson from OpenAI about what "open" means. Neither is evidence. The shapes a disappearance like this can take are limited, and it is worth naming them plainly. A repository can be deleted deliberately, made private, removed by GitHub for a policy or legal reason, or taken down by its owner after a security incident. A rename would have left a redirect, not a 404. A move to another organisation would have left a trace in the search results. None of those traces exist. Four related repositories vanishing at once, with no announcement and no redirect, looks like a deliberate act by someone with access. Deliberate by whom, and for what reason, is not something the public evidence answers.
Here is what that means for you, in order of how much it should worry you. If you install ONNX Runtime from PyPI or NuGet, keep going. Those channels are untouched, and 1.32.0 is there today. If your build clones the repository, it is already failing, and it will keep failing until Microsoft says something or the repository comes back. If you contribute to the project, or you have open pull requests or issues there, they are unreachable right now, and there is no public place to ask where they went. And if your company vets its dependencies by pointing at a GitHub page, that page is a 404 this morning, which is the kind of thing that makes a compliance review very interesting.
The practical steps are dull and they are the right ones. Pin the version you use instead of floating on "latest": 1.32.0 is the current release, and a pinned version does not care whether a repository exists. If you build from source, keep a vendored copy or a mirror you control; a repository you do not own is a dependency you do not control, and this morning is the demonstration. Watch the project's own site and Microsoft's channels for an explanation rather than the speculation threads, and do not migrate to a fork until there is an official word. A fork that appeared overnight has no history you can check.
The strangest part of this story is the silence. A 22,000-star project does not usually vanish without a word from anyone, and as of 00:18 UTC on 18 November, nobody from Microsoft has said one in public. Either there is a good reason and it will be explained, or there is a bad reason and it will be explained later. Until then, the facts are these: the code is gone from GitHub, the packages still install, and the people who depend on it are waiting for someone to say what happened.
P.S. Everything I write stays free — that part doesn't change. But if this one was worth something to you, you can buy me a coffee ☕ (one-time or monthly, both work). It covers the API credits and hosting behind these experiments — and honestly, it's also the nudge that gets the next one started on the evenings I'd otherwise skip it. — Salam
Comments
Join the discussionNo comments yet. Be the first to comment.






