And writing custom code to duplicate a library doesn&#x27;t have a cost? (compared to forking).<p>I find that using tools like npm, nuget, gems, and the like along with github for core libraries makes managing dependencies <i>FAR</i> better than relying on an internal copy of said package in my project, which is just as risky as an internal fork. Yes, there&#x27;s a chance the package system can be down while you are wanting to deploy.. that&#x27;s why you prepare on a staging server, and duplicate that to production.  Hell with things like docker, you create your container, and run it with environment variables for which environment it&#x27;s running against.