Microsoft's ONNX Runtime repository has been missing from GitHub since late November 17. According to a fix merged into the xLights project, starting around 22:20 UTC that day, github.com/microsoft/onnxruntime, its API endpoint and every release asset returned 404. An issue filed on the ONNX project the same day reported that microsoft/onnxruntime-swift-package-manager had gone too. byteiota, citing RuntimeWire, reports that seven or more related repositories went too. The repo had no archive banner, redirect or notice. A thread about the outage reached 452 points on the Hacker News front page on November 18.
Why it matters: ONNX Runtime is Microsoft's widely used engine for running machine-learning models on CPUs, GPUs and other accelerators. A lot of software pulls its prebuilt native libraries straight from GitHub release URLs at build time, and some apps do so at runtime. All of those downloads now fail.
What broke
Public issue trackers show the damage:
| Project | What failed |
|---|---|
| xLights | Ubuntu CI stopped because onnxruntime-linux-x64-1.24.4.tgz couldn't be downloaded |
| c3-skill | Release builds failed, and installs without a cached library lost semantic search |
| ACE-Step-Studio | The lyrics-sync pack download fails on an ONNX Runtime 1.31.1 asset (song creation still works) |
The c3-skill issue also points out a separate weakness: its download had no checksum verification. That gap matters more if you're now swapping in a new source in a hurry.
What Microsoft has said
Microsoft hasn't explained the ONNX Runtime outage specifically. The timing lines up with the hijack of Microsoft's agent-framework package on PyPI on November 17 (our coverage). In its report on that hijack, a Microsoft spokesperson told The Register: "We have made some repositories private while we investigate malicious content." The Register also notes that neither Microsoft nor security researchers have connected the ONNX repo's disappearance to the malware campaign. The c3-skill and ACE-Step-Studio issues both say ONNX Runtime itself has not been reported as compromised.
byteiota reports that Microsoft also briefly pulled about 70 open-source repositories in June 2026. We haven't verified that claim independently.
Is it back? Reports disagree. Publicasta, updated November 19, says later checks found the repository reachable again but gives no time. When TechMeasured queried GitHub's search API at about 16:05 UTC on November 19, scoping the search to microsoft/onnxruntime returned an error saying the repository doesn't exist or isn't visible. Until Microsoft says otherwise, assume GitHub downloads are unreliable.
What still works
The DEV Community write-up, byteiota and Publicasta all report that these channels are unaffected:
- the
onnxruntimepackage on PyPI (pip install onnxruntimeworks) Microsoft.ML.OnnxRuntimeon NuGet- the onnxruntime.ai documentation
- other package channels (Publicasta lists Maven and CocoaPods)
Already-installed builds keep running. Apps that load the library they shipped with don't need GitHub at runtime.
What to do
- Find every GitHub fetch. Search build scripts, Dockerfiles, Makefiles and lockfiles for
github.com/microsoft/onnxruntime, and rungit config --file .gitmodules --listto check submodules. These steps come from the DEV audit. - Pull native libraries from NuGet instead. The xLights fix shows how: download
Microsoft.ML.OnnxRuntimeat the same version you had pinned, then take headers frombuild/native/includeand the library fromruntimes/linux-x64/native(orlinux-arm64). The package ships a single unversionedlibonnxruntime.so, so xLights renames it and recreates the.so.<version>and.so.1symlinks the GitHub tarball used to provide. The rest of the build then works unchanged. - Pin and verify. Record a sha256 for each artifact you mirror, as the c3-skill fix plans to. Don't let CI quietly fall back to
latestor nightly builds, and don't switch to an unofficial fork just because the official repo is 404 (Publicasta). - Mirror what you depend on. Use
git clone --mirrorfor source and keep a local cache of release assets and wheels. Prefer your mirror, with the public URL as a fallback. The DEV piece also suggests a weekly CI job that blocks github.com to prove builds still work without it. - If you use
agent-framework, check our guide linked above. That incident did involve stolen credentials.
What to watch
Watch for a statement from Microsoft or the ONNX Runtime maintainers saying whether the repository was made private for a security review and when it will return. If it comes back, compare tags and release-asset hashes against copies you already have before trusting new downloads.
Sources
- GitHub — xLights PR #7388: Linux CI falls back to NuGet for ONNX Runtime when GitHub 404s github.com
- GitHub — onnx/onnx issue #8842: Onnxruntime has disappeared? github.com
- The Register — Microsoft's official Python agent framework hijacked to distribute malware theregister.com
- DEV Community — Microsoft/onnxruntime is 404. Here is the audit we ran on our own pipeline dev.to
- byteiota — Microsoft's ONNX Runtime is gone from GitHub byteiota.com
- Publicasta — ONNX Runtime GitHub 404: what developers should check publicasta.com
- GitHub — c3-skill issue #77: release builds fail after microsoft/onnxruntime was removed github.com
- GitHub — ACE-Step-Studio issue #75: ONNX Runtime downloads fail github.com