DeepSource
Dashboard Resources Pricing Discover Directory Log in

Run your first analysis.

Find thousands of code security and quality issues in your codebase, before they end up in production.

Start now
All analyzers Go
Go

Go

By DeepSource

Use Analyzer
Docs
Discuss
Use consistent method receiver names SCC-ST1016
Style

As our codebase grows, eventually we'll need to refactor some of it. For example, consider moving pieces of code between levels abstractions or

Poorly chosen name for variable of type time.Duration SCC-ST1011
Style

time.Duration values represent an amount of time, which is represented as a count of nanoseconds. An expression like 5 * time.Microsecond yields the value 5000. It is therefore not appropriate to suffix a variable of type time.Duration with any time unit, such as Msec or Milli.

Poorly chosen name for error variable SCC-ST1012
Style

It is recommended that the error variables that are part of an API should be named as errFoo, ErrSomethingBad, ErrKindFoo or BazError.

A switch's default case should be the first or last case SCC-ST1015
Style

For better readability, always place default of switch as first or last case.

Non-idiomatic comment formatting GO-C4004
Style

Comments should have a space between the // and the comment text