November 18, 2026

ONNX Runtime disappeared from GitHub without warning

ONNX Runtime disappeared from GitHub without warning

Earlier today, Microsoft’s ONNX Runtime repository disappeared from GitHub without warning.

For most users, this probably did not matter. The standard Python install uses pip install onnxruntime, and the PyPI packages were still available.

But some builds depend directly on GitHub source, release files or C/C++ artifacts. For those builds, the dependency was suddenly gone.

That is the useful reminder here.

Pinning a dependency tells your build which version to use. It does not guarantee that version will still be available later.

You can solve that by vendoring dependencies into your own repository, keeping your own artifact storage or putting a cache between your build and the upstream source. The important part is having your own copy of the inputs needed to build your software.

We recently wrote about a similar case where installing sharp through npm still depended on a libvips archive hosted on GitHub Releases.

Read the previous GitHub file-cache post

StableBuild is another way to do this without maintaining the caches yourself. It can preserve external files, Docker images, packages from PyPI, Ubuntu, Debian and Alpine, Hugging Face files and other build dependencies.

ONNX Runtime happened to disappear today. Next time it could be something your build depends on.

Whether you vendor dependencies yourself or use a service like StableBuild, keep the inputs you need to build your software again.

Create a free StableBuild account and start preserving the external dependencies your builds rely on.