You must log in or register to comment.
Very weird behaviour for a language infrastructure. I’m not familiar with go, but couldn’t you setup your own module repository with e.g. nexus and crawl your needed modules, and block incoming traffic from the go “crawler”?
Go uses the GOPROXY env var to determine which proxy it hits, and defaults to Google’s proxy. Typically the only time people set that env var is when their org runs its own module proxy, or when they set it to direct to bypass the module proxies entirely.
Google has royally fucked up NPM and Go Modules smh
Looks like Google is trying to monopolize on the repository hosting…