G103
Use of unsafe calls should be audited.
Go is a very powerful language that makes you write performant code while having a lot of verification. Still, developers can make issues. Thankfully, the Codiga Static Code Analysis engine checks your Go code and flags the most important issues.
Use of unsafe calls should be audited.
Potential file inclusion via variable
Expect WriteFile permissions to be 0600 or less
Deferring unsafe method "Close" on type "*os.File"
Use of weak cryptographic primitive
TLS InsecureSkipVerify set true.
Blocklisted import crypto/md5: weak cryptographic primitive
Subprocess launched with variable
Expect file permissions to be 0600 or less
strings.Title has been deprecated since Go 1.18. Use golang.org/x/text/cases instead.
Value never used
Value refers to the result of a failed type assertion and is a zero value, not the value that was being type-asserted.
Error string should not be capitalized
Unused field.
Unnecessary assignment to the blank identifier
Hardcoded credentials
Bind to all interfaces
Audit errors not checked
Url provided to HTTP request as taint input
SQL query construction using format string/string concatenation
SQL query construction using format string/string concatenation
Profiling endpoint is automatically exposed on /debug/pprof
Expect directory permissions to be 0750 or less
Weak crypto primitive
exported function should have comment or be unexported
should omit type string from declaration of var
Blocklisted import crypto/des: weak cryptographic primitive
File traversal when extracting zip/tar archive
Packages should have comments.