Ask HN: What do bad Go codebases look like?

I've worked in the past with PHP, Java, Python, and JS/TS. The worst aspect of typed programming languages in large codebases was, without a doubt, the lack of types. The biggest issue with Java and TS wasn't the languages themselves but the frameworks used: too much magic in Spring Boot, difficulty running things locally, and tons of dependencies (libraries).

I've never worked in a Go codebase professionally, so I was wondering how bad Go codebases look.