Hacker News Reader

Until your tooling automatically makes a request to a now-untrusted server and trusts its response...

The Go tooling won't do that if you configure it properly (e.g. via a 'replace' directive in your go.mod or https://go.dev/ref/mod#goproxy-protocol)

Any tool that automatically assumes that a URL in a Go module import is 'trusted' is just a broken tool.

And if any tooling ever gets executed without the proper replace directive...

Any tooling that looks at Go module imports should respect the contents of go.mod.

If you haven't added a replace directive to your go.mod, then you certainly haven't replaced all instances of the old URLs with updated ones.

Go mandates lockfiles, called go.sum