> You should rather look at go.mod file no. the whole point of go.sum is to see everything. you could have a go.mod with a single item, but if that item is a g

> You should rather look at go.mod file no. the whole point of go.sum is to see everything. you could have a go.mod with a single item, but if that item is a giant module with hundreds of third party imports (as in this case), its quite misleading. > I've seen much, much worse worse, as a daily Go user I'd say it's fine uh where? I am a daily Go user, both professional and personal. and this is one of the most bloated modules I have ever seen.