Hacker News Reader

Go doesn't mitigate that somehow. You get the code that you specify, not the code that someone else has decided is better.

In practice, for both npm and Go dependencies, you'll get a Dependabot PR that upgrades the dependency for you. Obviously that is Github-specific, so if you're on a different platform, you'll have to subscribe to security updates in some other way. I am guessing there are many services that you can subscribe to that do the same thing.

Some big security hole is introduced in one of thousands of dependencies, npm gets the insecure version on next npm install while Go is stuck in the tested secure version. How difficult is that to see? I'm not the one to believe in conspiracy theories but this is just nuts.

Until the secure version is tested, as it should be for anything you deploy to production.

I'm not sure why you think deploying untested updates is a good idea?