FYI - ONNX will automatically exfiltrate data about your application with no way to opt out other than building it from source with telemetry disabled. Maybe you could block DNS too.
Not to take away from the fact that I don't like that this was done, but in my experience development on ONNX has been pretty slow recently. I moved away from a few months back because I felt bug fixes were coming in pretty slow, despite being reported.
> The ONNX Runtime (ORT) is the most widely used engine for serving deep
learning models in production. It is common for people to download ONNX
models from public repositories, such as Hugging Face, and to serve them to
their customers without too much scrutiny. In March 2026, we noticed a
parser flaw: an ONNX model can cause ORT to read from arbitrary file paths
(or memory addresses) without validations.
The closest/furthest ahead fork I could find is https://github.com/intel/onnxruntime for anyone else needing it, though that's with Intel's OpenVINO modifications
We found out about this this morning, when evals started failing in our pipelines. I've been looking around, but it doesn't seem like there was any advance warning about this.
Does anyone know why or how a repository with 22k stars just went dark?
If I understand your implication, that's not what "supply chain attack" normally means. That term means attacking the mechanism that delivers your packages to deliver a different, more compromised, package. If the package itself is already compromised then that's just a straightforward dependency vulnerability.
That would be my guess also. About 6 months ago the azure-functions-host repo disappeared for a while (I got a concerning automated email from GitHub from my forked repo citing a ToS violation).
Considering Microsoft co-developed ONNX with Facebook... I think that the more likely scenario is they took it dark after learning that it has security issues, but they should really have left a message or something, this is amateur hour tier. GitHub repos should let you leave a "Sorry we've hidden our repo, we learned about security issues" which kind of doesn't help anyone either... since now they have to find help elsewhere, and fall victim to sketchy 'forks' from other people...
I do wish I could pay some money for a package manager intermediary that "magically" handles things (for example defaulting to not promoting things until 2 weeks have passed), has better perf, and generally just does the right things.
Of course I wouldn't pay _that_ much money for it.
Aren't there other ONNX runtimes out there? A quick google search shows a few written in Rust: Tract, RTen, WONNX, Burn&Candle. Also, IIRC there's a Julia-based one as well.
Have used it with wasm and it's lovely, but I was kindof disappointed to learn internally it's basically another serialisation format. I imagined gigabytes of generated Rust code hehe
The graph is converted into Rust code that calls Burn APIs but the weights are converted into Burn's format, called burnpack (similar to safetensors but instead of JSON we use CBOR for weights meta data).
How odd. https://onnxruntime.ai is still up, and the packages still appear to be on PyPI, Maven Central etc. Guess I won't submit the PR I was working on tonight then.
Source: https://opensourcemalware.com/blog/agent-framework-pypi-comp...
[0]: https://phrack.org/issues/73/backdoor-attacks-against-machin...
Does anyone know why or how a repository with 22k stars just went dark?
You never know when it's going to vanish
Of course I wouldn't pay _that_ much money for it.
Though I'm pretty sure their enterprise pricing is "give us a call." Maybe your last sentence was a nod to this.
I maintain this project at the moment.
It convert ONNX models into native, backend-agnostic Burn code for inference and fine-tuning.
> https://github.com/syntax-syndicate/onnxruntime
Check the web archive link for commit hashes, the syntax-syndicate fork seems to be the remaining legit fork.
[1] https://web.archive.org/web/20261113082932/https://github.co...
https://mvnrepository.com/artifact/com.microsoft.onnxruntime...