Microsoft's ONNX Runtime has disappeared from GitHub
Microsoft’s popular ONNX Runtime machine learning engine and several related GitHub repositories abruptly went private, breaking builds and pipelines that depended on them. Developers speculate about security incidents and supply-chain risks, especially after reports that Microsoft’s Agent Framework package was compromised, and a company statement confirmed repositories were hidden while “malicious content” is investigated. The event has renewed scrutiny of Microsoft’s telemetry practices and highlighted the fragility of relying on third-party hosting, prompting calls for vendoring, internal mirrors, and alternative ONNX runtimes.
Repo disappearance and immediate impact
- ONNX Runtime and several related Microsoft GitHub repos suddenly returned 404, with no advance public warning.
- CI/eval pipelines depending on the repo started failing.
- The ONNX spec repo is still up, as are packages on PyPI, Maven Central, and the official onnxruntime.ai site, but source and examples are gone.
- Multiple associated repos (genai, extensions, training/inference examples, Swift, benchmarks, GitHub Actions) also vanished or went private.
Security incident and malicious content investigation
- Several commenters suspect a security issue or compromise, especially since Microsoft’s
agent-frameworkrepo and its PyPI package were reported as compromised with credential-stealing malware. - Later in the thread, a news article is cited where Microsoft states they “made some repositories private while we investigate malicious content.”
- There is mention of a previously disclosed ONNX Runtime parser flaw (described in Phrack) that was patched in an earlier release; some think it is unlikely to be the direct cause here.
- Some speculate about compromised admin or contributor accounts; others suggest repo consolidation, but this is criticized as an unacceptable way to migrate.
Forks, mirrors, and alternative runtimes
- Community members point to forks (notably one that matches archival commit hashes) and mirrors (including SourceForge), alongside warnings that random archives may contain malware.
- Intel’s fork and other runtimes (Rust-based Tract, RTen, WONNX, Burn/Candle, a GoMLX path, etc.) are discussed as potential replacements, with some maintainers present in the thread.
- Several users note they already moved away from ONNX Runtime due to slow bugfixes and weaker CPU performance, praising alternatives like Candle.
Telemetry and privacy concerns
- ONNX Runtime’s telemetry is criticized as unexpected for software often assumed to be offline.
- Others clarify distinctions: ONNX vs ONNX Runtime, platform differences, and that telemetry can be disabled via environment variables or build options, although there were past bugs around this.
Dependency management lessons
- Many highlight vendoring, internal artifact proxies (Artifactory, Nexus, StableBuild, etc.), and blocking direct internet downloads in CI as essential to survive upstream deletions and compromises.