The same is true of a encyclopedia. If you try to read it directly, word after word, it is boring. However, if you treat it as a reference, as the OP is asking for in Go code, it can be helpful and possibly inspiring.
Honestly, I don't find that very helpful. These, same as all that Hashicorp stuff, are pretty big and quite domain-specific projects, that are somewhat difficult to conceptualize about what they even do. As if the only thing go is being used for are all that distributed virtualization stuff.
Maybe at some point it is nice to look at them, but they don't look very approachable to me, if I just want to take a look at how code is normally written in go beyond some AoC-exercises. Like useful common patterns and such.