For junior, particularly first job, candidates their GitHub (if they have one) is something I look at very closely. They get points for knowing what a VCS is,

For junior, particularly first job, candidates their GitHub (if they have one) is something I look at very closely. They get points for knowing what a VCS is, points for creating an account, having anything on it, more if the stuff is any good, and they also get points for community activity like filing issues. It really establishes whether the candidate has ever touched the technology and it shows initiative. There are other ways they can show this but GitHub is really easy. I find it generally more informative than whiteboards which I have rarely ever done. For more senior candidates, I still look, still like to see at least a little activity (for instance, do you keep an eye on the repos of critical dependencies for your current project?), but generally there is less differentiation unless there is something truly impressive. I haven't ever penalized a candidate for the low quantity or quality of what they put there. I think it would be stifling. For me I just collect the positives (unless there is anything truly alarming, which I've never encountered).