Ground Truth.
AI, checked against the source.

News · 2026-11-18

ONNX Runtime’s GitHub repository became unavailable while packages stayed online

Microsoft’s canonical ONNX Runtime GitHub repository returned 404 responses in the dossier’s November 18 checks, while existing packages remained listed in major package registries. The cause was not established, leaving source-based builds and issue tracking uncertain without proving that the inference runtime itself has been withdrawn.

Key facts

ONNX Runtime is a cross-platform engine for running machine-learning models. Applications may depend on a prebuilt Python, .NET or browser package even when developers obtain source code from a different place. That distinction matters when a repository disappears: a warehouse can still contain packaged goods after the factory’s public front door becomes inaccessible.

The dossier checked GitHub’s release endpoint, tags, issues and raw README as well as the core repository API. Those endpoints returned 404, and Microsoft’s public organization search did not show the canonical core repository. A 404 is an observation about access, not a diagnosis. It cannot by itself distinguish deletion, conversion to private access or a repository-specific platform action.

GitHub’s status API reported all systems operational at the recorded check, weakening a theory of a broad outage at that moment without resolving the repository’s situation. The official ONNX Runtime documentation remained readable and continued to link to GitHub. Its continued existence does not establish that development or support will continue.

Package distribution was a separate story. PyPI, NuGet and npm metadata showed existing releases. The researchers checked registry metadata and artifact links, but did not download or execute packages. A listed artifact can support an existing pinned installation; it does not guarantee future updates, a reproducible source build or access to GitHub release assets.

The Hacker News item described the project as having “disappeared from GitHub.” That is a fair description of the observed public access failure, but not an explanation of its cause. The dossier could not read the discussion bodies in its later verification pass, so proposed community explanations remain unverified.

For engineering teams, the immediate question is which parts of their build actually depend on the canonical repository or GitHub tags. Registry-pinned installs, source clones, issue triage and reproducibility have different exposure. The record supports checking those dependencies; it does not support asserting that the project has ended or that everyone must migrate.

The package versions also have different meanings across ecosystems. PyPI and NuGet listed version 1.32.0, while npm identified 1.31.1 as its stable latest release and separately listed development builds. That does not demonstrate that the browser package is broken or that the projects follow identical release schedules. Registry metadata establishes what was listed when checked, not the quality of a particular build.

The timing is equally limited. The stable Python files were timestamped before the public discussion, but the exact time the repository first became inaccessible was not established. Consequently, a package timestamp cannot prove whether the team did or did not release anything after the access failure began. The state of the project’s continuous integration is also unknown from the checked surfaces.

For an organization that depends on this runtime, a proportionate response starts with an inventory. Identify applications using prebuilt packages, jobs that fetch GitHub source or tags, and processes that require access to issues or release notes. Confirm that pinned artifacts can be obtained through approved channels and that build records identify the versions used. Those checks address operational uncertainty without assuming a cause or recommending an unsupported migration. The distinction also illustrates a broader software supply-chain lesson: availability of a binary package and availability of its corresponding source are related but independently observable facts. The recorded check is a dated snapshot; later changes require fresh verification before publication.


Primary source, verified: read the paper →

Key questions

Was ONNX Runtime removed from package registries?

No. The checked PyPI, NuGet and npm registries still listed existing packages.

Did Microsoft delete the repository?

The observed 404 does not establish whether it was deleted, made private or affected by another repository-level action.
Cite this

APA

Ground Truth. (2026, November 18). ONNX Runtime’s GitHub repository became unavailable while packages stayed online. Ground Truth. https://groundtruth.day/news/onnx-runtime-github-unavailable-packages-remain.html

BibTeX

@misc{groundtruth:onnx-runtime-github-unavailable-packages-remain,
  title  = {ONNX Runtime’s GitHub repository became unavailable while packages stayed online},
  author = {{Ground Truth}},
  year   = {2026},
  month  = {nov},
  url    = {https://groundtruth.day/news/onnx-runtime-github-unavailable-packages-remain.html}
}

Topics: open-source · infrastructure · supply-chain

Comments are replies to this story on Bluesky — reply with any Bluesky account to join in.