News for hackers. Stuff that matters.
Re:Microsoft's ONNX Runtime has disappeared from GitHub by dangoodmanUT on Tuesday November 17, 2026 @07:53PM (#50540449)
This is why we vendor everything.

You never know when it's going to vanish

Re:Microsoft's ONNX Runtime has disappeared from GitHub by KirinDave on Tuesday November 17, 2026 @07:58PM (#50540499)
If it were me, I would take the hint and maybe not trust a vendored version right now?
Re:Microsoft's ONNX Runtime has disappeared from GitHub by cjbgkagh on Tuesday November 17, 2026 @08:29PM (#50540720)
I believe vendoring in this context means forking it and serving it from your own repo.
Re:Microsoft's ONNX Runtime has disappeared from GitHub by katbyte on Tuesday November 17, 2026 @10:37PM (#50541545)
No that’s forking, vendoring usually means keeping a local copy of a library in /vendor that is automatically committed - rust and golang have first class support for this
Re:Microsoft's ONNX Runtime has disappeared from GitHub by kenferry on Tuesday November 17, 2026 @11:05PM (#50541741)
But if we think they took it down because of security issues…
Re:Microsoft's ONNX Runtime has disappeared from GitHub by rtpg on Tuesday November 17, 2026 @08:59PM (#50540942)
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.

Re:Microsoft's ONNX Runtime has disappeared from GitHub by rwiggins on Tuesday November 17, 2026 @09:16PM (#50541032)
Doesn't Artifactory provide exactly that? Along with having a bunch of features that are generally the right things.

Though I'm pretty sure their enterprise pricing is "give us a call." Maybe your last sentence was a nod to this.

Re:Microsoft's ONNX Runtime has disappeared from GitHub by esafak on Tuesday November 17, 2026 @09:42PM (#50541189)
I have not tried it myself: https://github.com/artifact-keeper
Re:Microsoft's ONNX Runtime has disappeared from GitHub by pjmlp on Wednesday November 18, 2026 @01:01AM (#50542414)
I don't get it, this is exactly how I have been mostly working since around 2010.

Nothing that lands on CI/CD pipelines is able to download anything directly from Internet, rather internal repos based on Nexus, Artfactory and similar.

Additionally everything that gets uploaded into them needs to have an approval process for the most part.

So, not only already exists, it is an intermediate process, and you can even pay depending on the features.

Re:Microsoft's ONNX Runtime has disappeared from GitHub by kreco on Wednesday November 18, 2026 @06:19AM (#50544900)
It baffles me that this is not the default.

I mean, sure for hobby project you don't want to setup/pay some intermediate repos.

But for anything else you just want control, if new version of an app is released, someone needs to actively bring it to the intermediate repository.

This is tangential, but that's also why being able to import a package from a git url in some language is extremely risky (your github repo could change owners at any time). At least the code should only know about the package id, and whatever "package manager" is install should link it to a repository.

Re:Microsoft's ONNX Runtime has disappeared from GitHub by duskdozer on Thursday November 19, 2026 @04:17AM (#50557803)
The git url could point to a location that you control.
Re:Microsoft's ONNX Runtime has disappeared from GitHub by kreco on Thursday November 19, 2026 @07:33AM (#50559276)
Yes, but should be safe by default, and then you can remove some safety net for convenience, being fully aware of the trade off.
Re:Microsoft's ONNX Runtime has disappeared from GitHub by malikolivier on Wednesday November 18, 2026 @02:55AM (#50543140)
Such solutions exist. Some people are building it on their own. Some people just commit all their dependencies in their repository.

If you want it enforced for a whole team, with caching on top, that's where registry proxies come in (Artifactory, Nexus, and similar). The big ones take real effort to set up, while lighter ones may be all you need.

Vendoring your dependencies into the repo is the low-tech option that survives an upstream repo vanishing.

Disclosure: I work at a company which sell such solutions.