One thing that struck me as painfully obvious about this is that the actual coding aspect of someone's job is only a small fraction of what makes them a good h

One thing that struck me as painfully obvious about this is that the actual coding aspect of someone's job is only a small fraction of what makes them a good hire. Not to mention, they might have JavaScript or what-ever language is good for an open source part of a system, but if they're working in DevOps, DB guru, etc. none of that comes through in this. I don't think I'd call this a GitHub Resume, more of a formatted GitHub summary that could be part of someone's Resume. Sure, if you're inundated with so many resumes that you can't decide where to start (doubt this is a problem most companies have) this might be a good place to start.