No need to buy anything, it's an MIT-licensed project, and a trivial implementation under the hood to boot. If I wasn't learning Go while writing it, I think it would take all of 5-10 minutes to replicate (including deploying to prod)... :-)
What I wish GitHub would do is allow us to specify our own GA profile in project settings and just add an extra two lines of JavaScript in their pages to beacon the right metrics directly to GA. They're already using GA on their pages, so adding an additional profile is trivial. [1]
A proper GA integration would eliminate the need to proxy requests, and give us (repo owners) more metrics: I'm most interested in referral information - aka, how are people finding my repo. Also, it would enable analytics on all pages (e.g. source files, etc).
GA is available on GitHub pages, there's an input for the ID in the settings. GitHub doesn't use GA, so there's also no need to implement two trackers, having an input for a GA ID in the repository settings would be enough.
Personally, I don't think Analytics is a good measurement of a project on GitHub, I would be more inclined to look at the number of clones, forks, downloads from the releases page, pull requests, and the number of commits being made.
