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.
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.
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.
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.
You never know when it's going to vanish