Distro repositories (like the one you have on Debian / Ubuntu / Redhat etc) do this. They work on a different model, where only packages that are deemed "worth

Distro repositories (like the one you have on Debian / Ubuntu / Redhat etc) do this. They work on a different model, where only packages that are deemed "worthy" are included, and there's a small-ish set of maintainers that are authorized to make changes and/or accept change requests from the community. In contrast, programming language package managers like cargo, pip or npm let anybody upload new packages with little to no prior verification, and place the responsibility of maintaining them solely on their author. The distribution way of doing things is sometimes necessary, as different distributions have different policies on what they allow in their repositories, might want to change compilation options or installation paths, backport bug and security fixes from newer project versions for compatibility, or even introduce small code changes to make the program work better (or work at all) on that system. One example of such a repository, for the Alpine Linux distribution, is at https://github.com/alpinelinux/aports https://github.com/alpinelinux/aports