Microsoft’s ONNX Runtime repositories were reported missing from GitHub on November 17–18, 2026, leaving developers unable to reach source code and related project resources. The cause remained unconfirmed: the published observations showed unavailable repositories, not proof of a compromise, deliberate deletion or project shutdown.
Two technical sites documented repeated 404 responses for the main repository and several companion projects. By the later report’s check, at approximately 07:40 UTC on November 18, neither Microsoft nor GitHub had publicly explained the disappearance. Published packages and the project’s documentation remained accessible during those observations, according to Coding Is Love’s report.
That distinction matters because ONNX Runtime is the engine applications use to execute machine-learning models across different platforms. Microsoft’s official project site lists support for Python, C#, JavaScript, C++ and other languages, with deployment options spanning servers, mobile devices and browsers. Microsoft says the runtime powers AI features in Windows, Office, Azure Cognitive Services and Bing, alongside thousands of external projects.
An unavailable source repository can disrupt that ecosystem without stopping every application already using the runtime.
What the Published Checks Showed
The public trail begins with a Hacker News submission by user nvader, dated 23:18 UTC on November 17, 2026, according to the accompanying technical coverage. This was a developer report, not an announcement from Microsoft.
Nvader said their team discovered the problem:
“when evals started failing in our pipelines”
The author also said they had not found advance warning. That is a traceable account of one team’s experience; the available evidence does not identify the exact dependency or download step that failed.
AheadKit’s report recorded checks at 00:04 and 00:18 UTC on November 18. Both reportedly returned 404 responses for microsoft/onnxruntime. The report also identified missing generative-AI, inference-examples and training-examples repositories.
Coding Is Love subsequently reported another 404 at approximately 07:40 UTC. Its coverage also named microsoft/onnxruntime-swift-package-manager among the affected repositories.

Those observations establish multiple reported failures hours apart. They do not establish an uninterrupted outage throughout that period. Coding Is Love also relayed a PyMuPDF maintainer’s comment that the repository had become available again, while saying its own later check still failed. That disagreement leaves room for intermittent availability or differences between observations. This article covers the published checks, not a live status measurement.
The scope also appeared narrower than a general GitHub outage. AheadKit reported that Microsoft’s VS Code, TypeScript and Windows Terminal repositories remained accessible and that GitHub’s status page showed normal operation. That helps describe the apparent scope, but it cannot identify who changed access or why.
Public Discussion Outran the Explanation
The Hacker News thread reached 342 points and 73 comments in the supplied snapshot. Those figures document substantial attention on that forum, not a representative survey of ONNX Runtime users or the AI industry.
Several participants speculated about a compromise; another suggested repository consolidation around Microsoft announcements. Neither explanation was confirmed in the thread. The discussion also branched into telemetry and other security topics, which did not establish the cause of the missing repositories.
The useful distinction is between the developer’s reported failure and commenters’ proposed explanations. Nvader described a concrete workflow problem. Other participants tried to explain it without an official account. Treating those two categories as equally established would turn an availability story into an unsupported security allegation.
The absence of an explanation made the incident harder to assess. Developers could see that an important dependency’s public development resources were unreachable, but could not tell whether to expect a short interruption, a migration or a longer recovery.
Packages and Documentation Remained Available
Coding Is Love reported the following availability at approximately 07:40 UTC on November 18:
| Resource | Reported availability | Practical significance |
|---|---|---|
PyPI: onnxruntime | Version 1.32.0, uploaded November 13 | Python packages remained obtainable from the registry |
NuGet: Microsoft.ML.OnnxRuntime | Version 1.32.0 | The published.NET package remained available |
npm: onnxruntime-web | Version 1.31.1 | The browser-focused JavaScript package remained available |
| ONNX Runtime website and documentation | Online | Installation guidance and documentation remained reachable |
| Main GitHub repository and related projects | Reported 404 responses | Source access and repository-based workflows were affected |
| GitHub release downloads | Reported unavailable | Scripts fetching release assets could fail |
These are the versions and conditions reported by Coding Is Love, not a recommendation to upgrade to them. AheadKit separately reported downloading the Python 1.32.0 wheel and finding the NuGet package available during its earlier checks.
The package versions differ across ecosystems. Python and.NET both showing 1.32.0 does not mean the npm package should have the same version number, or that users should change their existing dependency choices.
A registry download and a GitHub download are separate retrieval paths. A build fetching a Python wheel from PyPI may succeed while another build, using the same runtime version but cloning its source, fails. A pipeline downloading a prebuilt archive from GitHub Releases can also fail even though a package registry still serves its own artifacts.
I’d use that retrieval path as the first troubleshooting distinction. The runtime’s name in a dependency list is less informative than the actual URL or registry the failing job contacts.
A 404 Is Not a Diagnosis
A public GitHub repository returning 404 does not reveal its underlying state. Deletion, a change to private visibility or a GitHub restriction can produce the same outward result, as .
Frequently Asked Questions
3 questions
1Was ONNX Runtime Confirmed to Be Compromised?
No. The published evidence documents repository-access failures and speculation. It does not confirm a compromise or identify the cause.