This snap falls into the problem space of a tool that is used to build things. In most cases these tools require access to the file system, albeit that is not the strict case for goreleaser as it just needs access to GOPATH; unless it uses CGO, where access to the actual development libraries would be needed.
I consider this tool to be just like snapcraft but with a focused view on only working on what it builds (go code) and also relate it to electron-builder in what it outputs, i.e.; a snap, deb, rpm, etc…
There are two views to this tool, how it is distributed itself and what it outputs. With regards to the latter, this tool already supports outputting to snaps, regardless of it being distributed as one and that is its own problem space in itself.
Distributing this tool as a snap with classic confinement would not change in any way how it is distributed today so I would +1 on that alone.