Q
Detector Library
Go detectors (45/45)
Useless if BodyChannel Guarded With MutexImproper Certificate ValidationUnvalidated S3 Bucket OwnershipResource LeakInsecure CookieWeak Random Number GenerationRedundant Equality CheckInsecure Ignore Host KeyUnsafe ReflectionUnchecked Batch Operation FailuresLambda Client ReuseOs Command InjectionUseless if ConditionalLog InjectionHttptrace FileServer As HandlerPprof EndpointCross Site Scripting (XSS)Not Recommended API UsageHidden GoroutineChannel Accessible By Non EndpointDecompression BombCross-Site Request Forgery (CSRF)Thread Safety ViolationInsecure ConnectionSQL InjectionDeprecated Key GeneratorExported Loop PointerServer Side Request Forgery (SSRF)Sensitive Information LeakInteger OverflowMissing PaginationInsecure CryptographyProtection Mechanism FailureNil Pointer DereferenceTemporary FilesXML External EntityInsecure File PermissionsAuthentication Bypass By Alternate NameCode InjectionImproper authenticationUse Filepath JoinPath TraversalWrite Pprof Profile OutputHardcoded true or false
Not Recommended API Usage High
Using deprecated Amazon Web Services (AWS) APIs and outdated client initialization in Go code can introduce security risks and quality issues. Initializing old S3 or Kinesis clients without proper configuration may leak credentials or have other security flaws. Calling unsupported APIs like GetRecords and ListObjects can lead to unexpected breaks when AWS fully retires those APIs. To improve quality and security, use the latest AWS SDK client initialization patterns and avoid APIs not currently recommended per the AWS documentation. This reduces technical debt and avoids known issues with outdated clients and APIs.
Detector ID
go/not-recommended-apis@v1.0
Category
Common Weakness Enumeration (CWE) 
-