News 3 min read

Microsoft's ONNX Runtime repository disappears from GitHub


Microsoft’s ONNX Runtime, the open-source engine many apps use to run machine learning models on servers, phones and in the browser, has vanished from GitHub. Since November 17, 2026, github.com/microsoft/onnxruntime returns “404 Not Found”, and neither Microsoft nor GitHub has said why. The packages people install from PyPI, NuGet and npm still work, but anything that builds ONNX Runtime from source or downloads files from its GitHub releases is breaking.

What happened

Developers noticed when their pipelines started failing. The Hacker News thread that put the story on the front page was posted at 23:18 UTC on November 17 by someone who said they found out “when evals started failing in our pipelines”, and that there seemed to be no warning beforehand. It reached more than 270 points within hours.

Issues opened the same day in other projects tell the same story:

  • In the ONNX project, issue #8842 says the ONNX Runtime repositories “have disappeared and this is breaking CI/CD systems”, and lists microsoft/onnxruntime and microsoft/onnxruntime-swift-package-manager as missing. It has no reply from a maintainer yet.
  • In PyMuPDF, which can use ONNX Runtime, issue #5287 asks whether the onnxruntime package on PyPI will keep being maintained. A PyMuPDF maintainer later replied that the repository was available again and closed the issue, but when we checked at about 07:40 UTC on November 18, github.com/microsoft/onnxruntime still returned a 404.
  • RuntimeWire reports that at least seven related repositories went with it, and that release downloads now return “not found”.

Microsoft has not posted an explanation, on GitHub or on the project’s site. Commenters on Hacker News have guessed at security clean-ups and a quiet end to the project, but nothing confirms any of it. A repository can disappear because it was deleted, made private, or disabled by GitHub; from the outside, all three look like the same 404.

What still works

We checked the package registries and the project’s website on November 18, 2026, at about 07:40 UTC:

Where What’s there
PyPI (onnxruntime) Version 1.32.0, uploaded November 13, 2026
NuGet (Microsoft.ML.OnnxRuntime) Version 1.32.0
npm (onnxruntime-web) Version 1.31.1
onnxruntime.ai and its docs Online

So pip install onnxruntime, dotnet add package Microsoft.ML.OnnxRuntime and npm install onnxruntime-web still work today. What doesn’t: cloning the repository, Git submodules that point at it, build scripts that download prebuilt binaries from its GitHub releases page, and links to its issues, code and examples. The PyPI listing’s own “Download” link still points to the repository’s tags page, which is now a 404 too.

What it means for developers

ONNX Runtime sits under a lot of software: Python inference code, .NET apps, and browser libraries that run models with WebAssembly, such as the one in our post on removing an image’s background in JavaScript. If you depend on it:

  • Pin the version you use now. Lock onnxruntime==1.32.0 (or whichever version you ship) in your requirements or lockfile, so a rebuild doesn’t pick up something unexpected while the project’s future is unclear.
  • Keep your own copy of the binaries. If CI downloads wheels, NuGet packages or release archives, cache them in your own artifact store or package mirror. Packages that are already published usually stay on PyPI, NuGet and npm even when the source repository is gone, but you don’t control that.
  • Replace GitHub release URLs. Scripts that fetch files from github.com/microsoft/onnxruntime/releases need to get the same files from a registry or from your cache instead.
  • Treat forks with care. Copies of the code are still on GitHub in forks, such as intel/onnxruntime. They are useful for reading code, but build from a fork only after checking which commit it is at and who controls it.
  • Watch for an announcement. Until Microsoft explains, assume the repository may come back, or may not. Avoid moving to another runtime in a hurry because of a 404 alone.

We’ll update this post when Microsoft or GitHub says what happened.

Sources