Github has had this type of problem before, and it seems that they handle it pretty well. I think as long as a single repository doesn't become a massive hotspo

Github has had this type of problem before, and it seems that they handle it pretty well. I think as long as a single repository doesn't become a massive hotspot, Github don't really mind. I'm pretty sure that go checks out dependencies direct from github for every application, so the precedent is there. Shards also caches the repositories globally, which is nice.